Grant calico-kube-controllers access to Networks - #5187
Merged
caseydavenport merged 1 commit intoAug 14, 2026
Conversation
The node controller's IPAM syncer watches Networks, and its syncer stays out of sync until that list succeeds.
caseydavenport
added
kind/bug
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.
Automatic host endpoints and LoadBalancer IP assignment stop being programmed on Enterprise clusters. kube-controllers has no permission to list networks, so its datastore syncer retries the list forever and never reaches in-sync, which leaves the node and load balancer controllers idle.
This grants get, list and watch on networks to the calico-kube-controllers cluster role.