This repository has been archived by the owner on May 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[elasticsearch] Add securityContext to keystore container #1195
Labels
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity since being marked as stale. |
ebuildy
added a commit
to ebuildy/helm-charts
that referenced
this issue
Dec 15, 2021
fix elastic#1195 , add a securityContext for the initContainer "keystore". The securityContext is the same than the main container.
4 tasks
jmlrt
added a commit
that referenced
this issue
Mar 4, 2022
fix #1195 , add a securityContext for the initContainer "keystore". The securityContext is the same than the main container. Co-authored-by: jmlrt <[email protected]>
jmlrt
added a commit
to jmlrt/helm-charts
that referenced
this issue
Mar 4, 2022
fix elastic#1195 , add a securityContext for the initContainer "keystore". The securityContext is the same than the main container. Co-authored-by: jmlrt <[email protected]>
jmlrt
added a commit
that referenced
this issue
Mar 7, 2022
fix #1195 , add a securityContext for the initContainer "keystore". The securityContext is the same than the main container. Co-authored-by: jmlrt <[email protected]> Co-authored-by: Thomas Decaux <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the feature:
Currently, only main container have a securityContext configurable via values.yaml (https://github.com/elastic/helm-charts/blob/master/elasticsearch/templates/statefulset.yaml#L223), in order to improve security, initContainer
keystore
(https://github.com/elastic/helm-charts/blob/master/elasticsearch/templates/statefulset.yaml#L173) should have it too.Describe a specific use case for the feature:
This is a good thing to match k8S best-practices, especially when using Fairwinds Polaris.
The text was updated successfully, but these errors were encountered: