-
Notifications
You must be signed in to change notification settings - Fork 3
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
epic: Complete InCluster Networking #95
Comments
@davidfestal @sttts I was having a look through the codebase to get an understanding of how #113 might be solved by creating a NetworkPolicy in each namespace. One that would "lock down by default between workspaces, but allow namespace comm for the same workspace" Some related discusssion in slack here https://kubernetes.slack.com/archives/C021U8WSAFK/p1667469578560679 A few thoughts:
My instinct is to create a default NetworkPolicy in every namespace that gets transformed when synced downstream. |
Here is the current take on this (still need to formalize it in an issue / EPIC):
We did not contemplate enabling the use-case when communications would be allowed between namespaces of originating from different KCP workspaces |
/transfer-issue contrib-tmc |
TL;DR
Extend the limited In Cluster Network support provided in PR kcp-dev/kcp#1708, in order to add:
Progress tracking #
EPIC detailed issues and overall progress can be tracked with the following project view
Work Items
The text was updated successfully, but these errors were encountered: