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/config which 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-reaper to /etc/cassandra-reaper/config and update them there to add all the necessary settings.
This solution is backwards compatible with pods running with no specific security context.
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.