You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I got the infromation that HyperShift uses etcd backend for tenant Kubernetes control-planes and you have your own internal implementation for etcd-clusters management.
Let me inform you that we've initiated a group effort to create a generic, multi-purpose etcd-operator. Currently, the project is in its early development phase, so there's a good opportunity for you to make influence on the project.
Our development process is open, and we are in kubernetes/community#7796 with sig-etcd about the possibility of making this the official version under Kubernetes-SIGs. Our goal is to bring together all potential adopters.
We would be pleased if you could present your official stance on this initiative and respond to the following questions:
Whether your project requires an etcd-operator at all.
Would you like to adopt and start using it once a stable version is released?
How important is it to you that the project continues to develop under the control of the official sig-etcd?
Would you be interested in joining the development and discussions to help address architectural challenges?
We welcome any other ideas and suggestions you have regarding this initiative.
The text was updated successfully, but these errors were encountered:
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
openshift-cibot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Aug 8, 2024
Hey, I got the infromation that HyperShift uses etcd backend for tenant Kubernetes control-planes and you have your own internal implementation for etcd-clusters management.
Let me inform you that we've initiated a group effort to create a generic, multi-purpose etcd-operator. Currently, the project is in its early development phase, so there's a good opportunity for you to make influence on the project.
https://github.com/aenix-io/etcd-operator
Our development process is open, and we are in kubernetes/community#7796 with sig-etcd about the possibility of making this the official version under Kubernetes-SIGs. Our goal is to bring together all potential adopters.
We would be pleased if you could present your official stance on this initiative and respond to the following questions:
We welcome any other ideas and suggestions you have regarding this initiative.
The text was updated successfully, but these errors were encountered: