Add securityContext to the user-supplied containers #390
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
ymmt2005
previously approved these changes
Mar 16, 2022
46bf36a to
0851e16
Compare
Signed-off-by: Masayuki Ishii <masa213f@gmail.com>
0851e16 to
2a8e4dd
Compare
|
@ymmt2005 |
|
@masa213f |
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.
moco v0.11.0 introduced a bug that it did not set
runAsUserandrunAsGroupin the user-supplied containers.In an environment that Pods are restricted to run as a non-root user, this would prevent running mysql pods.
https://kubernetes.io/docs/concepts/policy/pod-security-policy/#users-and-groups
https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
Signed-off-by: Masayuki Ishii masa213f@gmail.com