Description
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.