[prometheus-node-exporter] Add dnsPolicy configuration option #6439
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
When hostNetwork is true (the default), users may need to set dnsPolicy to 'Default' or 'ClusterFirstWithHostNet' to avoid DNS resolution issues or 'Nameserver limits exceeded' warnings when Kubernetes tries to combine host DNS with cluster DNS. This adds a dnsPolicy value that allows users to explicitly set the pod's DNS policy, similar to the existing dnsConfig option. Signed-off-by: sashanicolas <[email protected]>
sashanicolas
requested review from
gianrubio,
zanhsieh and
zeritti
as code owners
zanhsieh
approved these changes
Jan 1, 2026
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
Adds a
dnsPolicyconfiguration option to the prometheus-node-exporter chart.Problem
When
hostNetwork: true(the default), Kubernetes defaults todnsPolicy: ClusterFirst, which prepends cluster DNS to the host's DNS servers. If the host has 3 nameservers configured, this results in 4 total nameservers, exceeding the limit and triggering:Solution
Add a
dnsPolicyvalue (similar to the existingdnsConfig) allowing users to set:Default- use only host DNS (appropriate when pod doesn't need cluster DNS)ClusterFirstWithHostNet- prefer cluster DNS with host DNS fallbackChanges
Chart.yaml: version bump 4.49.2 → 4.50.0values.yaml: AddeddnsPolicy: ""with documentationtemplates/daemonset.yaml: Added template logic to renderdnsPolicywhen setUsage
Related
Signed-off-by: sashanicolas [email protected]