karmada-io/karmada

Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 12th, 2026
Created on November 10th, 2020
Open Issues & Pull Requests: 851 (+0)
GitHub issues: Enabled
Number of forks: 1,189
Total Stargazers: 5,621 (+0)
Total Subscribers: 71 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 hours
Mean response time: 15.0 days
90th percentile: 6.7 days
Tracked items: 700

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 78% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 46% of tracked open issues have had no activity in three months. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 272
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 424 days
Stale 30+ days: 238
Stale 90+ days: 188

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • kind/feature (236)
  • kind/bug (168)
  • kind/question (135)
  • help wanted (75)
  • good first issue (23)
  • kind/cleanup (19)
  • kind/flake (18)
  • kind/documentation (3)

Detailed Description

Karmada 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.

Karmada solves the problem of orchestrating workloads across multiple Kubernetes clusters and cloud providers by providing a centralized control plane that speaks Kubernetes-native APIs. It works through a control plane consisting of an API server, controller manager, and scheduler that manage the lifecycle of attached clusters and propagate resources to them. The system uses a policy-driven approach where PropagationPolicy objects define how resources should be distributed, and a series of controllers handle cluster attachment, resource selection, binding creation, and execution across member clusters.

Organizations managing applications across multiple clouds or on-premises infrastructure should consider Karmada if they want to avoid vendor lock-in and maintain a consistent Kubernetes experience without rewriting applications. The tool suits hybrid cloud and multi-cloud scenarios where centralized management, automatic failover, cross-cluster load balancing, and multi-dimensional high availability across regions, availability zones, and clusters are required. Built-in policy sets address common patterns including active-active deployments, remote disaster recovery, and geo-redundant configurations. Karmada integrates with mainstream cloud providers and supports clusters in public clouds, on-premises environments, and edge locations.

The project maintains active development across its core components with regular updates to the control plane architecture and scheduling capabilities. The codebase shows ongoing refinement of the policy and binding controllers that form the foundation of resource distribution. Work continues on expanding cluster management features and the execution layer that delivers resources to member clusters. The project benefits from contributions across multiple organizations and maintains focus on the multi-cluster scheduling and orchestration capabilities that differentiate it from single-cluster Kubernetes management.