Grant calico-apiserver RBAC for managedclusters/status#4843
Merged
caseydavenport merged 1 commit intoMay 21, 2026
Merged
Conversation
Without this, voltron's status updates fail when the aggregated apiserver proxies the write through to the backing CRD as its own service account.
rene-dekker
approved these changes
May 21, 2026
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.
Follow-up to #4823.
The original change granted calico-manager (voltron's SA) update access to managedclusters/status on the projectcalico.org aggregated API. That gets voltron past its own auth check, but when the aggregated apiserver proxies the status write through to the backing CRD it does so as the calico-apiserver SA, which still lacked managedclusters/status on crd.projectcalico.org. The result is voltron loops on:
ManagedClusters then never get a Connected condition, es-kube-controllers treats them as disconnected, and the LicenseKey never reaches the managed cluster. Verified on a live management cluster that adding this permission lets voltron set the status and unblocks the license sync.