Repository navigation
Conversation
OpenShift's default SCC, restricted-v2, assigns each pod a UID and fsGroup from its namespace's range and refuses a runAsUser or fsGroup outside it. RustFS and k8s-credential-provider pin theirs, so a default install on OpenShift never starts them. Leave runAsUser, runAsGroup and fsGroup unset when the cluster serves security.openshift.io/v1, so these pods run in group 0 like other pods with an assigned UID. Other clusters render the same manifests as before. RustFS runs as an arbitrary UID with a group-writable /data; it logs to stdout when it cannot write /logs. Signed-off-by: Ada Lundhe <adalundhe@lundhe.audio>
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.
OpenShift's default SCC, restricted-v2, assigns each pod a UID and fsGroup from its namespace's range. It refuses a runAsUser or fsGroup outside that range. The chart pins RustFS to 10001 and k8s-credential-provider to 65532, so OpenShift refuses both pods at admission until an admin grants another SCC.
The chart now leaves runAsUser, runAsGroup and fsGroup unset on these pods when the cluster serves
security.openshift.io/v1. Other clusters render the same manifests as before.helm templatecannot see the cluster, so the README says to pass--api-versions security.openshift.io/v1when rendering for OpenShift.Upgrade note: if you granted
anyuidto the RustFS ServiceAccount as a workaround, remove the grant.anyuidtakes priority over restricted-v2 and assigns no fsGroup, so a new RustFS PVC is not writable. Anonroot-v2grant does no harm, because restricted-v2 sorts ahead of it.Not covered: the kustomize manifests in
manifests/ate-install/andmanifests/egress-credential-injection/still pin these IDs.Tested:
helm templateoutput matchesmainbyte for byte for six value sets. With--api-versions security.openshift.io/v1, only the pinned IDs drop.main's templates, and when either template change is reverted./logs.helm lint,hack/render-manifests.sh --checkandhelm unittest charts/substratepass.AI use: written with Claude Code. A second agent session reviewed it and tried to break it.
🤖 Generated with Claude Code