Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

etcd-operator adoption #430

Closed
kvaps opened this issue Apr 9, 2024 · 0 comments
Closed

etcd-operator adoption #430

kvaps opened this issue Apr 9, 2024 · 0 comments

Comments

@kvaps
Copy link
Contributor

kvaps commented Apr 9, 2024

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:

  • 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.

@clastix clastix locked and limited conversation to collaborators Apr 9, 2024
@prometherion prometherion converted this issue into discussion #431 Apr 9, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant