Skip to content
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

Closed
astoycos opened this issue Apr 28, 2021 · 8 comments
Closed

Create a new kubernetes-sigs/network-policy-api repo #5747

astoycos opened this issue Apr 28, 2021 · 8 comments
Assignees
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@astoycos
Copy link
Contributor

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.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 28, 2021
@astoycos
Copy link
Contributor Author

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 28, 2021
@astoycos
Copy link
Contributor Author

astoycos commented Apr 28, 2021

/assign @caseydavenport @aojea

@astoycos
Copy link
Contributor Author

cc @abhiraut @Dyanngg

@aojea
Copy link
Member

aojea commented Apr 28, 2021

@astoycos I think that you have to open the issue in kubernetes/org, there is also a template for that
see this example kubernetes/org#1292

Once you submit the request, it should be good to announce it in the sig-net mailing list too , see
https://groups.google.com/g/kubernetes-sig-network/c/Ev2FX74bACA/m/jtw65R5ADAAJ

@mrbobbytables
Copy link
Member

@aojea is right 👍 please open an issue on k-org

@mrbobbytables
Copy link
Member

I'm going to close this for now, when you're ready - please open an issue over in k-org.

Thanks!

/close

@k8s-ci-robot
Copy link
Contributor

@mrbobbytables: Closing this issue.

In response to this:

I'm going to close this for now, when you're ready - please open an issue over in k-org.

Thanks!

/close

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.

@astoycos
Copy link
Contributor Author

ACK, will do Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

5 participants