Skip to content
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

Closed
dholbach opened this issue Mar 20, 2019 · 13 comments
Closed

New repository: addon-operators #630

dholbach opened this issue Mar 20, 2019 · 13 comments
Assignees
Labels
area/github-repo Creating, migrating or deleting a Kubernetes GitHub Repository

Comments

@dholbach
Copy link
Member

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

@dholbach dholbach added the area/github-repo Creating, migrating or deleting a Kubernetes GitHub Repository label Mar 20, 2019
@luxas
Copy link
Member

luxas commented Mar 20, 2019

👍

@nikhita
Copy link
Member

nikhita commented Mar 20, 2019

/assign

@nikhita
Copy link
Member

nikhita commented Mar 20, 2019

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.

@nikhita
Copy link
Member

nikhita commented Mar 20, 2019

Oh also...what should be the one-line description for the repo?

@nikhita
Copy link
Member

nikhita commented Mar 20, 2019

I will then assign the teams appropriate access to the repo.

This is done.

@dholbach
Copy link
Member Author

Oh also...what should be the one-line description for the repo?

"Addon operators for Kubernetes clusters"?

Not very witty, but let's add it for now and move on from there.

@dholbach could you create a PR to add this new subproject to sigs.yaml in the community repo?

Will do.

@timothysc
Copy link
Member

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

@timothysc
Copy link
Member

Also ensure the SCL leads have admin rights to that repo.

@nikhita
Copy link
Member

nikhita commented Mar 20, 2019

"Addon operators for Kubernetes clusters"?

Done.

Please ensure the OWNERs files are updated appropriately to follow standard subproject formats.

Done.

Also ensure the SCL leads have admin rights to that repo.

Created #634. @luxas was not part of kubernetes-sigs, so I've added him there. @timothysc can you add lgtm?

@timothysc
Copy link
Member

/lgtm

Thx @nikhita !

@nikhita
Copy link
Member

nikhita commented Mar 20, 2019

/lgtm

Oops, you commented on the issue :)

@nikhita
Copy link
Member

nikhita commented Mar 21, 2019

All done!

/close

@k8s-ci-robot
Copy link
Contributor

@nikhita: Closing this issue.

In response to this:

All done!

/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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/github-repo Creating, migrating or deleting a Kubernetes GitHub Repository
Projects
None yet
Development

No branches or pull requests

5 participants