This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
Use local volumes instead of hostpath volumes #366
Merged
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.
local
volumes rather thanhostpath
volumes in our e2e tests.cassandra
directly, bypassing the container image entry point #347, where I'm bypassing the Docker image entrypoint script.chown
to makecassandra
user the owner of/var/lib/cassandra
, and then execsu cassandra cassandra
PodSecurityContext
andSecurityContext
RunAsUser
andFSGroup
.FSGroup
doesn't work for HostPath volumes (Add FSGroup support to HostPath volumes. kubernetes/kubernetes#39438)local
volume provisioner does applyFSGroup
when mounting the volume.Fixes: #351
Release note: