[bitnami/redis-cluster] Added support to generate custom certificate for redis#14323
[bitnami/redis-cluster] Added support to generate custom certificate for redis#14323navneet066 wants to merge 9 commits into
Conversation
Signed-off-by: navneet066 <navneet.nandan@widas.in>
Signed-off-by: navneet066 <navneet.nandan@widas.in>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> Signed-off-by: navneet066 <navneet.nandan@widas.in>
Signed-off-by: navneet066 <navneet.nandan@widas.in>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> Signed-off-by: navneet066 <navneet.nandan@widas.in>
Signed-off-by: navneet066 <navneet.nandan@widas.in>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> Signed-off-by: navneet066 <navneet.nandan@widas.in>
|
Hello @navneet066, could you provide me how you have tested these changes to reproduce it, please? |
|
This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution. |
Signed-off-by: corico44 <42420333+corico44@users.noreply.github.com>
|
@navneet066 Could you please resolve the conflicts in the tls-secrets.yaml file, please? |
|
@navneet066 ping! Could you please resolve the conflicts in the tls-secrets.yaml file so we can close this PR, please? |
|
This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution. |
|
This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution. |
|
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary. |
Description of the change
Added support to generate the custom certificate for the redis-cluster.
Benefits
Earlier: If we need to use the custom CA, We needed to create the kubernetes secret beforehand and fill the values.yaml accordingly.
Now: In this change, If we pass the base64 value of the CA and KEY in values.yaml, It will generate the Kubernetes secret accordingly for the redis-cluster.
Possible drawbacks
None known so far, previous behaviour can still be applied
Applicable issues
Additional information
Checklist
Chart.yamlaccording to semver. This is not necessary when the changes only affect README.md files.README.mdusing readme-generator-for-helm