fix(networkpolicy): use UDP/53 for DNS egress instead of named port - #19073
Merged
Conversation
Signed-off-by: fmlecpac <168742771+fmlecpac@users.noreply.github.com>
Signed-off-by: fmlecpac <168742771+fmlecpac@users.noreply.github.com>
jkroepke
reviewed
Aug 31, 2025
Contributor
Author
|
Added 53/TCP too. |
Jayclifford345
approved these changes
Sep 9, 2025
1 task
This was referenced Jun 23, 2026
felix0102
pushed a commit
to felix0102/loki
that referenced
this pull request
Aug 2, 2026
…rafana#19073) Signed-off-by: fmlecpac <168742771+fmlecpac@users.noreply.github.com>
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.
Hello,
What this PR does / why we need it:
The current NetworkPolicy template allows DNS egress using the named port dns.
However, not all clusters define a DNS service port with that name. This can cause the policy to block DNS traffic.
This PR replaces the named port with the standard numeric port 53/UDP, ensuring DNS resolution works consistently across clusters that use standard port for DNS service.
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
Should we make it configurable? (especially for clusters with a DNS service not on port 53)
Checklist
CONTRIBUTING.mdguide (required)featPRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.mddeprecated-config.yamlanddeleted-config.yamlfiles respectively in thetools/deprecated-config-checkerdirectory. Example PR