-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/opensearch] Add specific annotations to the svcHeadless and specific ConfigMap for ca.crt #29495
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Michée lengronne <[email protected]>
Sorry, the PR is not quite finished yet. I didn't want to lose it. |
Signed-off-by: Bitnami Containers <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
Thank you for initiating this pull request. We appreciate your effort. This is just a friendly reminder that signing your commits is important. Your signature certifies that you either authored the patch or have the necessary rights to contribute to the changes. You can find detailed information on how to do this in the “Sign your work” section of our contributing guidelines. Here you can see the specific steps for your case. Feel free to reach out if you have any questions or need assistance with the signing process. |
Description of the change
There are 2 changes:
Benefits
Specific annotations provide a way to add behaviour stricly scoped per svcHeadless Service. For instance, TLS cert creation.
ca.crt called from a specific ConfigMap provides a way to use the inject-cabundle feature of Openshift.
The 2 changes coupled together provide a way to automate the handling of certs through the Openshift API.
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm