base on Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration # Karmada  [](/LICENSE) [](https://github.com/karmada-io/karmada/releases/latest) [](https://slack.cncf.io) [](https://bestpractices.coreinfrastructure.org/projects/5301) [](https://securityscorecards.dev/viewer/?uri=github.com/karmada-io/karmada)  [](https://goreportcard.com/report/github.com/karmada-io/karmada) [](https://codecov.io/gh/karmada-io/karmada) [](https://app.fossa.com/projects/custom%2B28176%2Fgithub.com%2Fkarmada-io%2Fkarmada?ref=badge_shield) [](https://artifacthub.io/packages/krew/krew-index/karmada) [](https://clomonitor.io/projects/cncf/karmada) ## Karmada: Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration 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 an incubation project of the [Cloud Native Computing Foundation](https://cncf.io/) (CNCF). ## Why Karmada: - __K8s Native API Compatible__ - Zero change upgrade, from single-cluster to multi-cluster - Seamless integration of existing K8s tool chain - __Out of the Box__ - Built-in policy sets for scenarios, including: Active-active, Remote DR, Geo Redundant, etc. - Cross-cluster applications auto-scaling, failover and load-balancing on multi-cluster. - __Avoid Vendor Lock-in__ - Integration with mainstream cloud providers - Automatic allocation, migration across clusters - Not tied to proprietary vendor orchestration - __Centralized Management__ - Location agnostic cluster management - Support clusters in Public cloud, on-prem or edge - __Fruitful Multi-Cluster Scheduling Policies__ - Cluster Affinity, Multi Cluster Splitting/Rebalancing - Multi-Dimension HA: Region/AZ/Cluster/Provider - __Open and Neutral__ - Jointly initiated by Internet, finance, manufacturing, teleco, cloud providers, etc. - Target for open governance with CNCF **Notice: this project is developed in continuation of Kubernetes [Federation v1](https://github.com/kubernetes-retired/federation) and [v2](https://github.com/kubernetes-sigs/kubefed). Some basic concepts are inherited from these two versions.** ## Architecture  The Karmada Control Plane consists of the following components: - Karmada API Server - Karmada Controller Manager - Karmada Scheduler 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. 1. Cluster Controller: attach Kubernetes clusters to Karmada for managing the lifecycle of the clusters by creating cluster objects. 2. Policy Controller: the controller watches PropagationPolicy objects. When the PropagationPolicy object is added, it selects a group of resources matching the resourceSelector and creates ResourceBinding with each single resource object. 3. Binding Controller: the controller watches ResourceBinding object and create Work object corresponding to each cluster with a single resource manifest. 4. Execution Controller: the controller watches Work objects. When Work objects are created, it will distribute the resources to member clusters. ## Concepts **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. - Support 1:n mapping of Policy: workload, users don't need to indicate scheduling constraints every time creating federated applications. - With default policies, users can just interact with K8s API **Override Policy**: Karmada provides standalone Override Policy API for specializing cluster relevant configuration automation. E.g.: - Override image prefix according to member cluster region - Override StorageClass according to cloud provider The following diagram shows how Karmada resources are involved when propagating resources to member clusters.  ## Quick Start This guide will cover: - Install `karmada` control plane components in a Kubernetes cluster which is known as `host cluster`. - Join a member cluster to `karmada` control plane. - Propagate an application by using `karmada`. ### Prerequisites - [Go](https://golang.org/) version follows [go.mod](https://github.com/karmada-io/karmada/blob/master/go.mod#L3) - [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) version v1.19+ - [kind](https://kind.sigs.k8s.io/) version v0.14.0+ ### Install the Karmada control plane #### 1. Clone this repo to your machine: ```bash git clone https://github.com/karmada-io/karmada ``` #### 2. Change to the karmada directory: ```bash cd karmada ``` #### 3. Deploy and run Karmada control plane: run the following script: ```bash hack/local-up-karmada.sh ``` This script will do the following tasks for you: - Start a Kubernetes cluster to run the Karmada control plane, aka. the `host cluster`. - Build Karmada control plane components based on a current codebase. - Deploy Karmada control plane components on the `host cluster`. - Create member clusters and join Karmada. If everything goes well, at the end of the script output, you will see similar messages as follows: ```bash 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: - karmada-apiserver `kubectl config use-context karmada-apiserver` - karmada-host `kubectl config use-context karmada-host` The `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]` ### Demo  ### Propagate application In the following steps, we are going to propagate a deployment by Karmada. #### 1. Create nginx deployment in Karmada. First, create a [deployment](samples/nginx/deployment.yaml) named `nginx`: ```bash kubectl create -f samples/nginx/deployment.yaml ``` #### 2. Create PropagationPolicy that will propagate nginx to member cluster Then, we need to create a policy to propagate the deployment to our member cluster. ```bash kubectl create -f samples/nginx/propagationpolicy.yaml ``` #### 3. Check the deployment status from Karmada You can check deployment status from Karmada, don't need to access member cluster: ```bash $ kubectl get deployment NAME READY UP-TO-DATE AVAILABLE AGE nginx 2/2 2 2 20s ``` ## Kubernetes compatibility | | 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 | Kubernetes 1.27 | Kubernetes 1.28 | Kubernetes 1.29 | |-----------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| | Karmada v1.7 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Karmada v1.8 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Karmada v1.9 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Karmada HEAD (master) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | Key: * `✓` 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. ## Meeting Regular Community Meeting: * Tuesday at 14:30 UTC+8 (Chinese)(biweekly). [Convert to your timezone](https://www.thetimezoneconverter.com/?t=14%3A30&tz=GMT%2B8&). * Tuesday at 08:00 Pacific Time (English)(biweekly). [Convert to your timezone](https://www.thetimezoneconverter.com/?t=8:00&tz=PT%20%28Pacific%20Time%29). Resources: - [Meeting Notes and Agenda](https://docs.google.com/document/d/1y6YLVC-v7cmVAdbjedoyR5WL0-q45DBRXTvz5_I7bkA/edit) - [Meeting Calendar](https://calendar.google.com/calendar/embed?src=karmadaoss%40gmail.com&ctz=Asia%2FShanghai) | [Subscribe](https://calendar.google.com/calendar/u/1?cid=a2FybWFkYW9zc0BnbWFpbC5jb20) - [Meeting Link](https://zoom.com/my/karmada) ## Contact If you have questions, feel free to reach out to us in the following ways: - [mailing list](https://groups.google.com/forum/#!forum/karmada) - [slack](https://cloud-native.slack.com/archives/C02MUF8QXUN) | [Join](https://slack.cncf.io/) - [twitter](https://twitter.com/karmada_io) ## Talks and References | | Link | |------------------|-------------------------------------------------------------------------------------------------------------------------| | KubeCon(EU 2021) | [Beyond federation: automating multi-cloud workloads with K8s native APIs](https://www.youtube.com/watch?v=LJJoaGszBVk) | | KubeCon(EU 2022) | [Sailing Multi Cloud Traffic Management With Karmada](https://youtu.be/rzFbxeZQHWI) | | KubeDay(Israel 2023)| [Simplifying Multi-cluster Kubernetes Management with Karmada](https://www.youtube.com/watch?v=WCrIhRNBZ9I) | | KubeCon(China 2023) | [Multi-Cloud Multi-Cluster HPA Helps Trip.com Group Deal with Business Downturn and Rapid Recovery](https://www.youtube.com/watch?v=uninSyVBKO4) | | KubeCon(China 2023) | [Break Through Cluster Boundaries to Autoscale Workloads Across Them on a Large Scale](https://www.youtube.com/watch?v=22W1yrEJjtQ) | | KubeCon(China 2023) | [Cross-Cluster Traffic Orchestration with eBPF](https://www.youtube.com/watch?v=e4GA5e-C7n0) | | KubeCon(China 2023) | [Non-Intrusively Enable OpenKruise and Argo Workflow in a Multi-Cluster Federation](https://www.youtube.com/watch?v=gcllTXRkz-E) | For blogs, please refer to [website](https://karmada.io/blog/). ## Contributing If you're interested in being a contributor and want to get involved in developing the Karmada code, please see [CONTRIBUTING](CONTRIBUTING.md) for details on submitting patches and the contribution workflow. ## License Karmada is under the Apache 2.0 license. See the [LICENSE](LICENSE) file for details. ", Assign "at most 3 tags" to the expected json: {"id":"8714","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"