Allow mounting a volume to host the config and enable read only root FS #1507
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
burmanm
approved these changes
May 24, 2024
adejanovski
added a commit
that referenced
this pull request
Jun 12, 2024
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.
Fixes #1506
Instead of modifying files in
/etc/cassandra-reaper(which is located on the root FS), this PR uses a volume mount under/etc/cassandra-reaper/configwhich can be an emptyDir in Kubernetes. It will be writeable whatever the uid is and while keeping the root FS read only.The entrypoint scripts will copy the base cassandra.yaml and shiro.ini files from
/etc/cassandra-reaperto/etc/cassandra-reaper/configand update them there to add all the necessary settings.This solution is backwards compatible with pods running with no specific security context.