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 know that Kamaji uses etcd as one of possible backend stoarges for tenant Kubernetes control-planes. Right now you're developed and suggesting using kamaji-etcd helm chart .
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:
Hey, I know that Kamaji uses etcd as one of possible backend stoarges for tenant Kubernetes control-planes. Right now you're developed and suggesting using kamaji-etcd helm chart .
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: