Merged
Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
KevinKlaesRackspace2
approved these changes
Feb 17, 2026
stuartn
approved these changes
Feb 18, 2026
jcru
approved these changes
Feb 18, 2026
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
4 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.
So the short answer to this is that percona adds the keyfile from a volume mount in the statefulset -- however when it assigns permissions to that volume, it gives it permissions of 288(which is decimal, the octal format there is 440) As such, we can't tweak the permissions of the file in the location that percona mounts it
This copies the keyfile over to a temp dir where we can edit it, tweaks the permissions to give it 400, and then switches the argument in mongod to use the new path for the keyfile.
This makes mongo happier with starting this image