docs: warn what the volumes and securityContext override rights grant#14
Merged
Conversation
The allow-list gates the field, never its content: a delegated `volumes` right lets a user mount any Secret sitting in the workspace namespace, and `securityContext` includes `privileged: true`. Pod Security Admission does not backstop the first — `restricted` permits `secret` and `projected` volumes. Says so plainly on the accepted-limitations page, gives the mental model (delegate only to people you would trust with kubectl on the namespace), points at the alternatives that keep the admin in control, and names the cluster-side tools for partial trust. Cross-linked from the governance concept page, where the fields are chosen.
…ityContext bootstrap-governance still listed `volumes` as granted by default; chart 0.3.0 drops it, so its table and warning bullet are updated (an upgrade does not rewrite an existing policy CR). Also: `podSecurityContext` joins the two other unbounded rights, cephfs/rbd/iscsi scoped to non-`restricted` clusters, VAP redated to GA 1.30 / beta 1.28, and the "never references Secrets" note narrowed to env. Field-vs-content warning backported to v0.2.0, without the default-policy paragraph that would invert there.
DrummyFloyd
force-pushed
the
docs/override-rights-warnings
branch
from
July 25, 2026 03:49
19b63c6 to
8a4c092
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
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.
The allow-list gates the field, never its content: a delegated
volumesright lets a user mount any Secret sitting in the workspace namespace,
and
securityContextincludesprivileged: true. Pod Security Admissiondoes not backstop the first —
restrictedpermitssecretandprojectedvolumes.Says so plainly on the accepted-limitations page, gives the mental model
(delegate only to people you would trust with kubectl on the namespace),
points at the alternatives that keep the admin in control, and names the
cluster-side tools for partial trust. Cross-linked from the governance
concept page, where the fields are chosen.