Skip to content

[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
caseydavenport:auto-pick-of-#3866-origin-release-v1.38
Apr 5, 2025
Merged

[release-v1.38] Auto pick #3866: Set explicit DNS nameservers for calico/node when needed#3868
caseydavenport merged 8 commits intotigera:release-v1.38from
caseydavenport:auto-pick-of-#3866-origin-release-v1.38

Conversation

@caseydavenport
Copy link
Member

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 goldmane running as an in-cluster service.

For PR author

  • Tests for change.
  • If changing pkg/apis/, run make gen-files
  • If changing versions, run make gen-versions

For PR reviewers

A note for code reviewers - all pull requests must have the following:

  • Milestone set according to targeted release.
  • Appropriate labels:
    • kind/bug if this is a bugfix.
    • kind/enhancement if this is a a new feature.
    • enterprise if this PR applies to Calico Enterprise only.

@caseydavenport caseydavenport merged commit 7c2f664 into tigera:release-v1.38 Apr 5, 2025
2 checks passed
@caseydavenport caseydavenport deleted the auto-pick-of-#3866-origin-release-v1.38 branch February 9, 2026 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants