Default calico-node to the node's own DNS resolver - #5246
Open
caseydavenport wants to merge 1 commit into
Open
Conversation
calico-node runs before CNI is installed, so cluster DNS is not reachable when it starts. It now inherits the operator's DNS settings only when the operator has an explicit dnsConfig.
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.
Description
calico-node runs before CNI is installed, so cluster DNS is not reachable on the node when it starts. It inherited the operator's
ClusterFirstWithHostNetpolicy, leaving the CoreDNS ClusterIP as its only resolver. On a cluster where the Kubernetes API server is reachable only by name (EKS, AKS) that is circular, and the rollout wedges on the first node: CoreDNS needs CNI, and CNI is installed by calico-node.calico-node needs no cluster DNS of its own. The only Service it resolves is Goldmane, and the operator already gives it a host alias for that. So it defaults to the node's own resolver, and inherits the operator's
dnsPolicyanddnsConfigonly when the operator has an explicitdnsConfig, which stays the escape hatch for clusters that need something else.Fixes #1746
Fixes projectcalico/calico#10683
Release Note