-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow TCP DNS queries to kube-dns in the default deny policy #1096
Conversation
In cert-manager/website#1344 (comment) we're discussing whether the default Calico deny policy should also allow TCP DNS queries. Is there a reason to block them?
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Thanks for the submission, @wallrj. This subject of this is out of scope for a docs-only discussion. The question isn't "How should we be documenting X?" so much as "How should we do/write/build X?" I suggest you raise an issue with Project Calico and add link to this PR. |
Done: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a better policy than the existing one.
LGTM |
In cert-manager/website#1344 (comment) we're discussing whether the default Calico deny policy should also allow TCP DNS queries.
Is there a reason to block them?
Fixes: projectcalico/calico#8224
Product Version(s):
Issue:
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: