Made the connect helm chart Pod Security Standards compliant to standard Restricted #223
Conversation
This file contains hidden or 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
3deep5me
changed the title
|
I'm not really sure about your release strategy - feel free to commit on my branch or ping me if changes are needed. |
|
This change is required for running the connect server and operator in secure environments with least privilege - would love to see this in a release if possible - I currently have to make local patches to the helm chart. |
|
@edif2008 - would it be possible to have this PR considered? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See.
https://kubernetes.io/docs/concepts/security/pod-security-standards/
currently its not possible to have the chart running in a namespace with the policy Restricted:
https://kubernetes.io/docs/tasks/configure-pod-container/enforce-standards-namespace-labels/#applying-to-a-single-namespace