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

difference with karmada #315

Open
warjiang opened this issue Mar 11, 2024 · 2 comments
Open

difference with karmada #315

warjiang opened this issue Mar 11, 2024 · 2 comments

Comments

@warjiang
Copy link

warjiang commented Mar 11, 2024

I found many similar concepts shared with karmada, anyone can describe the advantage than karmada?

@mrlihanbo
Copy link
Collaborator

@warjiang Thanks for your interest and support on Kube Admial.

Kube Admiral and Karmada are both projects focused on multi-cluster management in Kubernetes environments, but they have different approaches and features.

As both of them are developed from Kubernetes Federation v2, some concepts will be similar. And they all have the basic capabilities such as multi-cluster application scheduling, application distribution, and differentiated configuration, etc.

But, Kube Admiral has been deployed in large-scale production environments and has undergone refinement in terms of stability, reliability and scalability. We look forward to your active participation in community development to further enhance and improve Kube Admiral.

@lowang-bh
Copy link

Does kubeAdmiral support control plane components‘ HA?I find karmada has a HA via external etcd。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants