fix(kuma-coredns): Don't allow access to privileged ports #26111
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.
Hitting this at random otherwise:
Running with escalated privileges does not help here.
Looking at Kuma's CoreDNS build repo, they aren't granting access to privileged ports, unlike upstream:
https://github.com/kumahq/coredns-builds/blob/987ec5457098249e8ffe280c8679bd70bcd7f7a5/Makefile#L28
Validated that this is a non-issue with our existing CoreDNS image