Karmada (Kubernetes Armada) is a Kubernetes management system that enables you to run your cloud-native applications across multiple Kubernetes clusters and clouds, with no changes to your applications. By speaking Kubernetes-native APIs and providing advanced scheduling capabilities, Karmada enables truly open, multi-cloud Kubernetes.
Karmada aims to provide turnkey automation for multi-cluster application management in multi-cloud and hybrid cloud scenarios, with key features such as centralized multi-cloud management, high availability, failure recovery, and traffic scheduling.
Karmada is a sandbox project of the Cloud Native Computing Foundation (CNCF).
K8s Native API Compatible
Out of the Box
Avoid Vendor Lock-in
Fruitful Multi-Cluster Scheduling Policies
Open and Neutral
The Karmada Control Plane consists of the following components:
ETCD stores the Karmada API objects, the API Server is the REST endpoint all other components talk to, and the Karmada Controller Manager performs operations based on the API objects you create through the API server.
The Karmada Controller Manager runs the various controllers, the controllers watch Karmada objects and then talk to the underlying clusters' API servers to create regular Kubernetes resources.
Resource template: Karmada uses Kubernetes Native API definition for federated resource template, to make it easy to integrate with existing tools that already adopt on Kubernetes
Propagation Policy: Karmada offers a standalone Propagation(placement) Policy API to define multi-cluster scheduling and spreading requirements.
Override Policy: Karmada provides standalone Override Policy API for specializing cluster relevant configuration automation. E.g.:
The following diagram shows how Karmada resources are involved when propagating resources to member clusters.
This guide will cover:
karmadacontrol plane components in a Kubernetes cluster which is known as
git clone https://github.com/karmada-io/karmada
run the following script:
This script will do the following tasks for you:
If everything goes well, at the end of the script output, you will see similar messages as follows:
Local Karmada is running. To start using your Karmada environment, run: export KUBECONFIG="$HOME/.kube/karmada.config" Please use 'kubectl config use-context karmada-host/karmada-apiserver' to switch the host and control plane cluster. To manage your member clusters, run: export KUBECONFIG="$HOME/.kube/members.config" Please use 'kubectl config use-context member1/member2/member3' to switch to the different member cluster.
There are two contexts in Karmada:
kubectl config use-context karmada-apiserver
kubectl config use-context karmada-host
karmada-apiserver is the main kubeconfig to be used when interacting with the Karmada control plane, while
karmada-host is only used for debugging Karmada installation with the host cluster. You can check all clusters at any time by running:
kubectl config view. To switch cluster contexts, run
kubectl config use-context [CONTEXT_NAME]
In the following steps, we are going to propagate a deployment by Karmada.
First, create a deployment named
kubectl create -f samples/nginx/deployment.yaml
Then, we need to create a policy to propagate the deployment to our member cluster.
kubectl create -f samples/nginx/propagationpolicy.yaml
You can check deployment status from Karmada, don't need to access member cluster:
$ kubectl get deployment NAME READY UP-TO-DATE AVAILABLE AGE nginx 2/2 2 2 20s
|Kubernetes 1.16||Kubernetes 1.17||Kubernetes 1.18||Kubernetes 1.19||Kubernetes 1.20||Kubernetes 1.21||Kubernetes 1.22||Kubernetes 1.23||Kubernetes 1.24||Kubernetes 1.25||Kubernetes 1.26|
|Karmada HEAD (master)||✓||✓||✓||✓||✓||✓||✓||✓||✓||✓||✓|
✓Karmada and the Kubernetes version are exactly compatible.
+Karmada has features or API objects that may not be present in the Kubernetes version.
-The Kubernetes version has features or API objects that Karmada can't use.
Regular Community Meeting:
If you have questions, feel free to reach out to us in the following ways:
|KubeCon(EU 2021)||Beyond federation: automating multi-cloud workloads with K8s native APIs|
|KubeCon(EU 2022)||Sailing Multi Cloud Traffic Management With Karmada|
|KubeDay(Israel 2023)||Simplifying Multi-cluster Kubernetes Management with Karmada|
For blogs, please refer to website.
If you're interested in being a contributor and want to get involved in developing the Karmada code, please see CONTRIBUTING for details on submitting patches and the contribution workflow.
Karmada is under the Apache 2.0 license. See the LICENSE file for details.