[release-1.12] Cherry-pick Fix coredns network policies. #3163
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.
How to categorize this PR?
/area neworking
/kind bug
/priority normal
What this PR does / why we need it:
Now they allow traffic from the Pod network. This is needed because traffic might come from the calico tunnel IP which is part of the Pod network.
Before this, Pods with
hostNetwork: true
anddnsPolicy: ClusterFirstWithHostNet
could not talk to coredns if they are running on a different Node than CoreDNS.Which issue(s) this PR fixes:
n/a
Special notes for your reviewer:
Cherry-pick of #3162
Release note: