[release-v1.38] Auto pick #3866: Set explicit DNS nameservers for calico/node when needed#3868
Merged
caseydavenport merged 8 commits intotigera:release-v1.38from Apr 5, 2025
Conversation
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
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.
Cherry pick of #3866 on release-v1.38.
#3866: Set explicit DNS nameservers for calico/node when needed
Original PR Body below
Description
In eBPF mode (and theoretically any time KUBERNETES_SERVICE_HOST is a domain name instead of an IP), calico/node needs explicit nameserver configuration in order to resolve the address. Inherit this from the operator pod's configuration itself.
This is needed as a consequence of adjusting the DNS policy on calico/node to ClusterFirstWithHostNet, which was done as part of enabling DNS resolution of
goldmanerunning as an in-cluster service.For PR author
make gen-filesmake gen-versionsFor PR reviewers
A note for code reviewers - all pull requests must have the following:
kind/bugif this is a bugfix.kind/enhancementif this is a a new feature.enterpriseif this PR applies to Calico Enterprise only.