REQUEST: Create etcd-manager repo

[hakman]

New repo, staging repo, or migrate existing

new

Is it a staging repo?

no

Requested name for new repository

etcd-manager

Which Organization should it reside

kubernetes-sigs

Who should have admin access?

justinsb, hakman, ahrtr, wenjiaswe, neolit123

Who should have write access?

justinsb, hakman, ahrtr, wenjiaswe, neolit123

Who should be listed as approvers in OWNERS?

justinsb, hakman, rifelpet

Who should be listed in SECURITY_CONTACTS?

justinsb, hakman

What should the repo description be?

No response

What SIG and subproject does this fall under?

sig-etcd + sig-cluster-lifecycle

Please provide references to appropriate approval for this new repo

April 2, 2024 Community Meeting:
[ahrtr] move etcd-manager into sig-etcd
https://github.com/kubernetes-sigs/etcdadm/tree/master/etcd-manager
Open to further discussion

Additional context for request

Moving etcd-manager from the etcdadm/etcd-manager repo to its own repo.

Would be nice if possible to do something like this for bootstrapping:
https://docs.github.com/en/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository

[hakman]

CC @justinsb @neolit123 @wenjiaswe @ahrtr @fabriziopandini @serathius @jmhbnz

[ahrtr]

+1 Thanks

[neolit123]

+1

[wenjiaswe]

/sig etcd

+1 from me, SIG Cluster Lifecycle and SIG etcd have been talking about this and we are in agreement. Thank you @hakman !

[justinsb]

/lgtm as a sig-cluster-lifecycle lead and an etcd-manager maintainer

[serathius]

/lgtm as SIG etcd lead

[jmhbnz]

+1 - Thanks @hakman.

[mrbobbytables]

sorry, this fell through the cracks a bit - I can provision a repo tomorrow. Which SIG should the subproject fall under for updating sigs.yaml purposes?

[hakman]

sorry, this fell through the cracks a bit - I can provision a repo tomorrow. Which SIG should the subproject fall under for updating sigs.yaml purposes?

@mrbobbytables SIG etcd. Thanks!

[mrbobbytables]

/assign

[mrbobbytables]

Repo has been created and fleshed out: https://github.com/kubernetes-sigs/etcd-manager
Once the two open PRs are merged this should be good to close 👍

One FYI - @ahrtr @wenjiaswe you will need to accept the k-sigs org membership to be added to the repo admin team

[hakman]

Thanks @mrbobbytables! 😄

[mrbobbytables]

everything has been done, going to go ahead and close this out 👍
/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

everything has been done, going to go ahead and close this out 👍
/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.