etcd-manager transition
Closed this issue · 4 comments
The kOps project would like to start running etcd-manager built from this repo. We can then lock the kopeio/etcd-manager repo and redirect PRs to this repo instead. This repo has better bot support, unambiguous community ownership etc.
We will likely mirror images to the kopeio area for a transition period, to avoid breaking people, but we expect k8s.gcr.io to become the primary distribution point.
I had previously suggested we should move away from bazel first, I no longer think this is the right thing to do. Despite the fact that k/k has recently moved away bazel, replacing the bazel build for etcd-manager is likely non-trivial so we can build using bazel from this repo initially. We can then do the bazel migration work inside this repository.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-contributor-experience at kubernetes/community.
/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.