etcd-operator adoption

[kvaps]

Hey, I know that Mayastor requires etcd for storing metadata. We noticed you're using bitnami/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 discussions 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.

[tiagolobocastro]

Hi @kvaps, I don't know much about the etcd-operator tbh.

If the aim of the operator is to make maintenance of the etcd easier, example: adding more replicas, replacing failed replicas etc then I think definitely would be something we'd look into!

Whether your project requires an etcd-operator at all.

Not sure atm, would need to dig into the operator a bit.

Would you like to adopt and start using it once a stable version is released?

If it does the maintenance I mentioned above then I think this is a possibility yes.

How important is it to you that the project continues to develop under the control of the official sig-etcd?

Not sure.

Would you be interested in joining the development and discussions to help address architectural challenges?

Personally I probably wouldn't have much spare time for development I'm afraid.