RBAC: grant update on /status for globalalerts, packetcaptures, securityeventwebhooks#4853
Merged
caseydavenport merged 1 commit intoMay 23, 2026
Conversation
Several SAs need to write to /status subresources but the ClusterRoles only grant access to the parent resource: - calico-apiserver SA: add globalalerts/status, packetcaptures/status, securityeventwebhooks/status (backing-storage rule) - calico-node SA (enterprise): add packetcaptures/status alongside the existing packetcaptures update verb - intrusion-detection-controller SA: add securityeventwebhooks/status for the webhooks-processor controller Surfaces on real-cluster e2e (gcp-kubeadm) as repeated 403s in intrusion-detection-controller and felix capture status writer.
rene-dekker
approved these changes
May 22, 2026
caseydavenport
added a commit
that referenced
this pull request
May 23, 2026
Several SAs need to write to /status subresources but the ClusterRoles only grant access to the parent resource: - calico-apiserver SA: add globalalerts/status, packetcaptures/status, securityeventwebhooks/status (backing-storage rule) - calico-node SA (enterprise): add packetcaptures/status alongside the existing packetcaptures update verb - intrusion-detection-controller SA: add securityeventwebhooks/status for the webhooks-processor controller Surfaces on real-cluster e2e (gcp-kubeadm) as repeated 403s in intrusion-detection-controller and felix capture status writer.
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
3 participants
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.
Several service accounts call UpdateStatus on Calico Enterprise CRDs but the operator-rendered ClusterRoles only list the parent resource, so the kube-apiserver rejects the writes with 403.
Adds the missing /status entries:
pkg/render/apiserver.go):globalalerts/status,packetcaptures/status,securityeventwebhooks/status. This is the SA that the aggregated calico-apiserver uses to write through to the underlying CRDs, so missing /status verbs here block every controller that calls UpdateStatus on these resources.pkg/render/node.go, enterprise-only rule):packetcaptures/statusalongside the existingpacketcapturesupdate verb. Felix's capture status writer (felix/capture_status_writer.go) calls UpdateStatus.pkg/render/intrusion_detection.go):securityeventwebhooks/status. The webhooks-processor controller runs in the IDC pod and writes status conditions on SecurityEventWebhook objects (see https://github.com/tigera/calico-private/pull/12079).Same pattern as #4759 (managedclusters/status). KinD CI doesn't catch these because of how operator RBAC is layered on KinD vs gcp-kubeadm; the failures show up as repeated 403s in the intrusion-detection-controller and felix logs on gcp-kubeadm BPF e2e runs.
Release note