-
Notifications
You must be signed in to change notification settings - Fork 693
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
REQUEST: Create repository kubernetes-sigs/multi-network-api #4996
Comments
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 |
/assign @shaneutt |
/assign @aojea @thockin @danwinship |
/approve |
/assign |
repo has been created dougbtv is not a k8s org member and cannot be added once those PRs are closed, it should be g2g 👍 |
All PRs are merged. Closing. /close |
@Priyankasaggu11929: 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-sigs/prow repository. |
New repo, staging repo, or migrate existing
new repository
Is it a staging repo?
no
Requested name for new repository
multi-network-api
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?
API for 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 API, that is the result of the subproject in SIG Network of the same name kubernetes/community#7048.
Additional context for request
No response
The text was updated successfully, but these errors were encountered: