[release-v1.42] Default calico-node to the node's own DNS resolver - #5247
Open
caseydavenport wants to merge 1 commit into
Open
[release-v1.42] Default calico-node to the node's own DNS resolver#5247caseydavenport wants to merge 1 commit into
caseydavenport wants to merge 1 commit into
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
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
Backport of #5246.
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, which deadlocks the rollout on a cluster where the Kubernetes API server is reachable only by name. It defaults to the node's own resolver instead, and inherits the operator's DNS settings only when the operator has an explicitdnsConfig.Release Note