[1952] Move security context in statefulsets/postgres to pod-level spec #1953
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
(pod security context) to support fsGroup and other settings which are not available at container-level security context.
edward2a
force-pushed
the
postgres-fsGroup
branch
from
da46643
to
0be1c11
Compare
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.
#1952
SUMMARY
Please see issue 1952.
This collides with PR #1947 so it's up to you whether to chose to expose both pod and container security context or stick to pod's only.
ISSUE TYPE
ADDITIONAL INFORMATION
Not much to say here, just enabling use of pod-level security context.