[DPE-10291]: rootless k8s#75
Open
skourta wants to merge 2 commits into
Open
Conversation
d816a1b to
0453bd7
Compare
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
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 pull request introduces and tests support for running the Valkey charm and its workload container as a non-root user. It updates configuration, file paths, and adds comprehensive integration tests to verify rootless operation and related behaviors.
Rootless operation and security improvements:
metadata.yamlis updated to specifycharm-user: non-root, and thevalkeycontainer is explicitly configured to run as a dedicated non-root user and group (uid/gid584792)./var/log,/etc/ssl/certs) to non-privileged, writable locations (charm_dir), ensuring compatibility with non-root operation.Testing and validation:
test_rootless.py) is added to verify that both the charm and workload containers do not run as root, lack sudo privileges, and that all relevant files (logs, certificates) are written to non-privileged locations. The tests also verify correct behavior during TLS enablement and after failover events.