Issue 623: add security context override to operator deployment (#623) #624
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change log description
Purpose of the change
Fixes #623
What the code does
Updated the Zookeper Operator helm chart to include the already existing securityContext section in the helm chart values.yaml file. Now, the securityContext values are correctly added to the operator Deployment. This ensures that the operator can run in a Kubernetes cluster where Pod Security Admission is enforced, and running in restricted mode.
How to verify it
Add custom settings to securityContext and/or podSecurityContext, and verify that the deployment object has been updated using:
kubectl -n <namespace> describe deployment zookeeper-operator