Hey, I know that Stolon might use etcd for storing metadata. While the main method is Kubernetes ConfigMap I'd like to 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 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.
Hey, I know that Stolon might use etcd for storing metadata. While the main method is Kubernetes ConfigMap I'd like to 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 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:
We welcome any other ideas and suggestions you have regarding this initiative.