-
Notifications
You must be signed in to change notification settings - Fork 382
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
✨ Adding DNS network policies #2423
✨ Adding DNS network policies #2423
Conversation
Skipping CI for Draft Pull Request. |
Could you provide more details about why it is a partial fix. What is implemented and what is not ? |
a642622
to
4e79820
Compare
a4f5b63
to
75610fc
Compare
not sure if it's a flake:
|
/test e2e |
1 similar comment
/test e2e |
75610fc
to
e8ab723
Compare
/hold I'm adding e2e tests. |
d52f788
to
527ee46
Compare
/unhold |
@sttts Do you want to approve ? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sttts The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
/restest |
/retest |
1 similar comment
/retest |
f242693
to
656ad4d
Compare
/lgtm |
1 similar comment
/lgtm |
/test e2e-sharded |
Summary
Restrict access to DNS pods to workspace associated to them. Also, make sure DNS pods have only access to CoreDNS pods.
This is enforced by create this networking policy, one per workspace:
Related issue(s)
Fix #1988
Related issue for cleaning up DNS-related resources: kcp-dev/contrib-tmc#80