-
Notifications
You must be signed in to change notification settings - Fork 274
fix(agent): apply pod-security labels from namespaceLabels again #5687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+56
−50
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#5550 came from operators, not from tenants. The complaint is that an operator writes pod-security labels in namespaceLabels and the agent silently drops them. Those deployments are exactly the ones in the d.client fallback: no fleet-default service account ships with the agent chart, so out of the box nothing is pinned. Restricting pod-security labels to the impersonated path would keep ignoring them for every one of the people who reported this, and silently at that.
The tenant path is the one that's already handled. Since #5351 the namespace is patched as the deployment's service account, so whether a bundle may touch its target namespace at all is decided by that account's downstream RBAC. That's a coarser gate than the prefix filter, since RBAC scopes the namespace and not individual labels, but it's the same gate Kubernetes itself uses for PSA, and it's the one operators control through Policy and allowedServiceAccounts. The filter is redundant there.
On the fallback path being an escalation: there's no service account in that path, so every manifest in the bundle is already applied with the agent's cluster-admin credentials. You're right that PodSecurity admission still applies to cluster-admin, so relabeling a namespace is a genuine capability gain, but the filter never prevented it. The same actor can point the bundle at a new namespace (Fleet creates it, and with no cluster-wide AdmissionConfiguration default it has no enforcement at all), ship a Namespace object carrying the labels, or adopt an existing namespace with helm.takeOwnership. All three go through the same credentials and the same API call, and none of them were ever filtered. This was the narrowest of four doors.
Where you have a point is the pruning. Dropping the exemption means a bundle that declares one unrelated label removes an admin-set enforce=restricted without ever naming a pod-security key. That's #4564's clobber bug reaching the labels where it matters most, and it's a surprise rather than a deliberate act.⚠️ But it's fixed by #5460 which rewrites the pruning to only remove what Fleet actually set. Without it, there is merit in keeping the pruning exemption in this PR.