kubernetes
REQUEST: Create repository kubernetes-sigs/multi-network
New repo, staging repo, or migrate existing
new repository
Is it a staging repo?
no
Requested name for new repository
multi-network
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
mskrocki, dougbtv, MikeZappa87,aojea
Who should have write access?
mskrocki, dougbtv, MikeZappa87,aojea
Who should be listed as approvers in OWNERS?
mskrocki, dougbtv, MikeZappa87,aojea
Who should be listed in SECURITY_CONTACTS?
mskrocki, dougbtv, MikeZappa87,aojea
What should the repo description be?
Repository for components handling Multi-Network feature.
What SIG and subproject does this fall under?
SIG Network
Please provide references to appropriate approval for this new repo
This is repository for the Multi-Network feature, that is the result of the subproject in SIG Network of the same name https://github.com/kubernetes/community/pull/7048.
Additional context for request
No response
This is repository for the Multi-Network feature API, that is the result of the subproject in SIG Network of the same name https://github.com/kubernetes/community/pull/7048.
let's add this to the sig network meeting agenda to discuss there
Discussed in sig-network meeting on Jun6th https://docs.google.com/document/d/1_w77-zG_Xj0zYvEMfQZTQ-wPP4kXkpGD8smVtW_qqWM/edit#bookmark=id.g5u0v9owdfdv
/lgtm
repo has been created teams added in #5078 updates to sigs.yaml: https://github.com/kubernetes/community/pull/7988
dougbtv is not a k8s org member and cannot be added mskrocki and MikeZappa87 are not currently members of k-sigs, so for now the teams only have @aojea to get this going.
once those PRs are closed, it should be g2g :+1:
@Priyankasaggu11929: Closing this issue.
In response to this:
All PRs are merged. Closing.
/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-sigs/prow repository.
