fix: set securityContext.fsGroup on minio pods#14
Merged
thesuperzapper merged 1 commit intoAug 8, 2023
Conversation
Signed-off-by: Mathew Wicks <[email protected]>
thesuperzapper
added
the
status/ready-to-merge
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR addresses permission issues that may be encountered for some kinds of PVC StorageClasses used by the MinIO pods by setting PodSecurityContext
fsGroupto1000.NOTE: this fix was already applied to MySQL, but was missed on the MinIO pods.