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
Create a new kubernetes-sigs/network-policy-api
repo
#5747
Comments
/sig network |
/assign @caseydavenport @aojea |
@astoycos I think that you have to open the issue in kubernetes/org, there is also a template for that Once you submit the request, it should be good to announce it in the sig-net mailing list too , see |
@aojea is right 👍 please open an issue on k-org |
I'm going to close this for now, when you're ready - please open an issue over in k-org. Thanks! /close |
@mrbobbytables: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
ACK, will do Thanks! |
After much discussion in the Network Policy API Meeting, on the KEP for Cluster Scoped Network Policy and in slack(dis 1 dis 2) we (the sig-network-policy subgroup within Sig-Network) have decided that the best way to iterate on Network Policy, such as with the cluster-scoped network policy and a possible Network Policy V2, is to create a repo which will serve to house CRDs supported by the group. This follows the same pattern completed by the Kubernetes Gateway API. It has also been agreed upon that this repo should be called
network-policy-api
as it relates to all future work involving k8's network security.This issue serves to open up further discussion from the greater Sig-Network group around how the internals (CRD groups, api approval process etc should work) and to hopefully get permission to create the new repository.
The text was updated successfully, but these errors were encountered: