Allow konnectivity agents to reach the Calico webhooks - #5212
Merged
caseydavenport merged 3 commits intoAug 18, 2026
Conversation
On AKS and GKE the apiserver proxies admission calls through those pods, so they arrived with a pod source IP and hit the deny rule.
tmjd
approved these changes
Aug 18, 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.
Description
On AKS and GKE the API server reaches in-cluster webhooks through konnectivity agent pods, so the admission call arrives at
calico-webhookswith a pod source IP. The policy we render denies every pod source on the webhook port, and the allow that precedes it matches thedefault/kubernetesservice, whose endpoint is the public control plane address. Result: everyprojectcalico.org/v3write times out on the tiered RBAC webhook.This adds an allow for the konnectivity agents ahead of the deny. AKS labels them
app: konnectivity-agentand GKE usesk8s-app, so the selector matches either.Found while running the e2e suite against AKS 1.36.2 with the v3 CRDs served directly. Adding this rule by hand took the run from 74 failures to zero.
Release Note