search

kubernetes / org

Meta configuration for Kubernetes Github Org
Apache License 2.0
240 stars 668 forks source link

REQUEST: Archive repo https://github.com/kubernetes-sigs/etcdadm #5013

Open neolit123 opened 4 weeks ago

neolit123 commented 4 weeks ago

Repository to archive

https://github.com/kubernetes-sigs/etcdadm

Repository and/or sig subproject owners that are approving this archival

@justinsb @dlipovetsky

When should this be done

anytime

Additional context for request

SIG CL is the owner the etcdadm subproject: https://github.com/kubernetes-sigs/etcdadm

the project was relatively low activity, but it contained one key component used by the kOps project - etcd-manager.

we opened the conversation on a ticket and on the SIG CL mailing list to archive the etcdadm repository: https://github.com/kubernetes-sigs/etcdadm/issues/395 https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/SH463K1CmHs

in the meantime we extracted etcd-manager to a new subproject repo that is now owned by SIG etcd: https://github.com/kubernetes-sigs/etcd-manager

what is left for us to do is archive etcdadm.

neolit123 commented 4 weeks ago

cc @fabriziopandini @vincepri @hakman

neolit123 commented 4 weeks ago

/sig cluster-lifecycle etcd

fabriziopandini commented 4 weeks ago

/lgtm

justinsb commented 4 weeks ago

cc @hakman

Two things I would ideally like to get done first, but aren't technically blocking:

1) We should decide whether we want to change the path of the image, as @neolit123 pointed out currently that it contains "etcdadm": registry.k8s.io/etcdadm/etcd-manager-slim:v3.0.20230925

2) It would be nice if we had the build pipelines working on the new repo, I don't think we've set them up yet. The concern is that if there's a CVE (or similar), it might slow down a rapid release.

hakman commented 4 weeks ago

@justinsb :

  1. For sure we will change the path to something like registry.k8s.io/etcd-manager/etcd-manager-slim. Not sure if registry.k8s.io/etcd-manager exists yet though.
  2. I think we can work on this in the next few weeks and should be relatively simple to get it working, assuming 1) is addressed. The risk should be minimal.
neolit123 commented 2 weeks ago

guithub-team, we are ready to proceed with this archival. PTAL when possible.

hakman commented 2 weeks ago
  1. It would be nice if we had the build pipelines working on the new repo, I don't think we've set them up yet. The concern is that if there's a CVE (or similar), it might slow down a rapid release.

@justinsb FYI, build pipelines are working on the new etcd-manager repo, so there is no blocker remaining for archiving the etcdadm repo.

neolit123 commented 5 days ago

k/community cleanup PR: