-
Notifications
You must be signed in to change notification settings - Fork 702
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
Need a apiserver-network-proxy for sig-cloud-provider #715
Comments
sig-cloud-provider isn't an organization. Do you mean @kubernetes-sigs ? |
/assign @andrewsykim |
Fixed |
👍 from me!! Would prefer |
I'm fine with apiserver-network-proxy. |
This would be really helpful to have pretty soon so we can start collaborating on the server-network-proxy code. Thanks! |
/assign |
For the record: treating #715 (comment) as approval. |
Created https://github.com/kubernetes-sigs/apiserver-network-proxy 🎉 Also created the PRs:
Once teams are granted access and kubernetes/community#3598 has merged, we can close this issue. |
Done. |
kubernetes/community#3598 has merged. /close |
@nikhita: 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. |
New Repo, Staging Repo, or migrate existing
New repo
Requested name for new repository
apiserver-network-proxy
Which Organization should it reside
Kubernetes SIGs
If not a staging repo, who should have admin access
cheftako, mcrute, anfernee, andrewsykim
If not a staging repo, who should have write access
cheftako, mcrute, anfernee, andrewsykim
If not a staging repo, who should be listed as approvers in OWNERS
cheftako, mcrute, anfernee, andrewsykim
If not a staging repo, who should be listed in SECURITY_CONTACTS
cheftako, mcrute, anfernee, andrewsykim
What should the repo description be
by default we will set it to "created due to (link to this issue)"
What SIG and subproject does this fall under in sigs.yaml
sig-cloud-provider and cloud-provider-extraction-migration
Approvals
Chatted with Andrew Sy Kim and Bowei Du. (SIG Cloud Provider and SIG Networking)
https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190226-network-proxy.md
Authoritative requirements are here: https://git.k8s.io/community/github-management/kubernetes-repositories.md
Additional context for request
This is intended to house the proto-type and later reference implementations for server network proxies. Amazon, Azure and Google have all indicated interest in helping in this effort. The server network proxy is a necessary step in extracting cloud provider specific code from the Kube API Server. Also the Networking, API Machinery and Cloud Provider SIGs have all agreed to the work.
The text was updated successfully, but these errors were encountered: