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

Use other storage instead of etcd for karmada-aggregated-apiserver and karmada-search #5025

Open
majoyz opened this issue Jun 6, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@majoyz
Copy link

majoyz commented Jun 6, 2024

What would you like to be added:
Use other storage(like metrics-server used) instead of etcd for karmada-aggregated-apiserver and karmada-search.

Why is this needed:
Currently, we use etcd as karmada-aggregated-apiserver and karmada-search's storage. If there's no etcd server expose(in some public cloud k8s clusters), we have to deploy an etcd in karmada cluster, is this necessary? Can we just store these resource(clusters and resourceregistry) in memory or other places without third party dependencies?

@majoyz majoyz added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: No status
Development

No branches or pull requests

1 participant