SYS-662 add node-local-dns cache from kubernetes distro#223
Merged
instantlinux merged 2 commits intomainfrom Sep 15, 2025
Merged
SYS-662 add node-local-dns cache from kubernetes distro#223instantlinux merged 2 commits intomainfrom
instantlinux merged 2 commits intomainfrom
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.
Summary of Changes
Defines in the k8s
Makefilethenodelocaldnsimport from kubernetes/kubernetes distribution repo to add a local DNS caching resolver on each node. The sequence:will add a daemonset and related services to add a DNS resolver at 169.254.0.10, and reconfigure kube-proxy to automatically redirect traffic (via
iptables) at 10.96.0.10 from all pods on all workers to the new address.A prometheus scraper for grafana is added here as well, to support dashboard 11759. And: bumped Prometheus version from 3.3.1 to 3.5.0.
Why is this change being made?
UDP traffic between k8s nodes isn't reliable, especially under load. This is the widely-documented workaround to improve DNS reliability.
How was this tested? How can the reviewer verify your testing?
Local testing.
Completion checklist