[release-v1.40] Use pod-network k8s service endpoint for non-cluster-host Typha#4841
Merged
caseydavenport merged 2 commits intoMay 22, 2026
Conversation
The non-cluster-host Typha deployment runs pod-networked but inherits KUBERNETES_SERVICE_HOST/PORT from the host-network endpoint. On MKE clusters that resolves to proxy.local:6444, which pods can't resolve, so the deployment crashloops with DNS timeouts during the iptables-to-eBPF migration. Strip those env vars so the NCH Typha falls back to the in-cluster kubernetes Service that kubelet injects into every pod.
caseydavenport
force-pushed
the
casey-nch-typha-podnet-v1.40
branch
from
06ab4fa to
9ac27ec
Compare
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
2 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.
This branch (and the corresponding Calico Enterprise v3.22.x line) doesn't have #4474 in it, so a direct cherry-pick of #4840 + #4846 doesn't apply cleanly. This is a minimal, self-contained backport that fixes the customer-reported failure mode without pulling the larger pod-network ServiceEndpoint refactor onto a stable branch.
The non-cluster-host Typha deployment runs pod-networked but inherits
KUBERNETES_SERVICE_HOST/PORTfrom the host-network endpoint. On MKE clusters that resolves toproxy.local:6444, which pods can't resolve, so the deployment crashloops with DNS timeouts during the iptables-to-eBPF migration. Strip those env vars intyphaEnvVarsNonClusterHostso the NCH Typha falls back to the in-cluster kubernetes Service that kubelet injects into every pod.Requested for inclusion in the v3.22.6 patch release.
Related: https://tigera.atlassian.net/browse/CI-1987