Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration


Why Karmada

K8s Native API Compatible

Zero change upgrade: from single-cluster to multi-cluster; Seamless integration of existing K8s tool chain

Open and Neutral

Jointly initiated by Internet, finance, manufacturing, teleco, cloud providers, etc. Target for open governance with CNCF

Avoid Vendor Lock-in

Integration with mainstream cloud providers; Automatic allocation, migration across clusters; Not tied to proprietary vendor orchestration

Out of the Box

Built-in policy sets for scenarios: Active-active, Remote DR, Geo Redundant

Fruitful Scheduling Policies

Cluster Affinity; Multi Cluster Splitting/Rebalancing; Multi-Dimension HA: Region/AZ/Cluster/Provider

Centralized Management

Cluster location agnostic; Support clusters in public cloud, on-prem or edge

How it Works

Karmada API server

● Provide REST endpoint for resource template and policies based on Kubernetes native API.

Karmada Controller

● Implements policy APIs, watches resources in the Karmada API server then talks to underlying clusters to create regular Kubernetes resources.

Karmada Scheduler

● Schedule resource template across clusters according to constraints and available resources.