Conversation
This makes our containers compliant with the "restricted" Pod Security Standard and any admission policies that require it. OpenShift already injects these today (and has done so in the past) so that's why I'm pretty certain our operators & products can deal with these.
lfrancke
marked this pull request as ready for review
October 3, 2026 21:37
This branch has not been deployed
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
1 participant
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.
Part of stackabletech/issues#645
The
with_stackable_defaultsbuilders now set what the restricted Pod Security Standard asks for.OpenShift's SCCs have been injecting exactly these for years, so nothing changes there and I'm fairly confident it's safe. On non-OpenShift Kubernetes a namespace enforcing
restrictedcurrently rejects our Pods. I tested that on k3d for the operator Deployments (not for the products but I'd expect the same there)Every operator already calls
PodSecurityContextBuilder::with_stackable_defaults, so the seccomp part only needs an operator-rs bump. The container part only kicks in once operators useSecurityContextBuilderfor each container, which none do yet. That'll be a follow-up.