-
Notifications
You must be signed in to change notification settings - Fork 692
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
New repository: addon-operators #630
Comments
👍 |
/assign |
Created https://github.com/kubernetes-sigs/addon-operators 🎉 After the postsubmit runs for #631, the teams will be created on GitHub. I will then assign the teams appropriate access to the repo. :) @dholbach could you create a PR to add this new subproject to sigs.yaml in the community repo? Once the teams are assigned access + the above PR gets merged, we can close this issue. |
Oh also...what should be the one-line description for the repo? |
This is done. |
"Addon operators for Kubernetes clusters"? Not very witty, but let's add it for now and move on from there.
Will do. |
Please ensure the OWNERs files are updated appropriately to follow standard subproject formats. e.g. - https://github.com/kubernetes-sigs/cluster-api/blob/master/OWNERS |
Also ensure the SCL leads have admin rights to that repo. |
Done.
Done.
Created #634. @luxas was not part of kubernetes-sigs, so I've added him there. @timothysc can you add lgtm? |
/lgtm Thx @nikhita ! |
Oops, you commented on the issue :) |
All done! /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 repository
Requested name for new repository
addon-operators
Which Organization should it reside
kubernetes-sigs
If not a staging repo, who should have admin access
@justinsb
If not a staging repo, who should have write access
@justinsb
If a new repo, who should be listed as approvers in OWNERS
@justinsb
If a new repo, who should be listed in SECURITY_CONTACTS
@justinsb
What should the repo description be
The cluster-addons sub-project was set up in the 2019-03-12 meeting of SIG Cluster Lifecycle
What SIG and subproject does this fall under in sigs.yaml
This is a new subproject for sig-cluster-lifecycle called cluster-addons
Approvals
/cc @luxas @timothysc
The text was updated successfully, but these errors were encountered: