Skip to content
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

Support the Kubernetes API as a topology service #5701

Closed
carsonoid opened this issue Jan 13, 2020 · 0 comments · Fixed by #5703
Closed

Support the Kubernetes API as a topology service #5701

carsonoid opened this issue Jan 13, 2020 · 0 comments · Fixed by #5703
Labels
Type: Enhancement Logical improvement (somewhere between a bug and feature)

Comments

@carsonoid
Copy link
Contributor

Feature Description

Right now running even a small Vitess installation in Kubernetes requires that the end user deploy and maintain a fully functional kv store. It seems to be a hurdle for initial adoption for many users.

Since the Kubernetes API is built on etcd and provides all the same primitives (get, update, delete, watch, lock) it should be possible to use the K8s as a topology service.

Use Case(s)

Any user running Vitess in Kubernetes.

@morgo morgo added the Type: Enhancement Logical improvement (somewhere between a bug and feature) label Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants