kumahq/kuma

🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 31 minutes ago
Added to GitGenius on September 17th, 2026
Created on March 13th, 2019
Open Issues & Pull Requests: 112 (+0)
GitHub issues: Enabled
Number of forks: 370
Total Stargazers: 4,005 (+0)
Total Subscribers: 57 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.0 days
Mean response time: 84.3 days
90th percentile: 283.1 days
Tracked items: 1,459

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 5% of issues opened in the past year have never received a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/bug" is answered fastest, typically in about 3 days, while "kind/design" waits about 7 weeks. Almost all tracked open issues have seen activity in the last three months. 91% of issues opened in the past year have since been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 67
New in 7 days: 12
Closed in 7 days: 13
Avg open age: 240 days
Stale 30+ days: 28
Stale 90+ days: 2

Recent activity

Opened in 7 days: 12
Closed in 7 days: 13
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • triage/accepted (1,094)
  • kind/feature (403)
  • kind/bug (335)
  • triage/pending (243)
  • kind/improvement (211)
  • triage/stale (208)
  • kind/cleanup (180)
  • breaking-change (125)

Detailed Description

Kuma is a service mesh that runs on Kubernetes, VMs, and across multiple zones using Envoy as its data plane proxy.

Kuma addresses the challenge of providing service connectivity, security, and observability across heterogeneous infrastructure by building on Envoy without requiring users to have Envoy expertise. It supports both single-zone and multi-zone deployments, automatically enabling cross-zone communication and propagating policies across clusters and clouds. The tool includes built-in policies for security, traffic control, service discovery, and observability, designed to reduce the operational complexity of running a service mesh across distributed teams and platforms.

Organizations running services on both Kubernetes and VMs should consider Kuma, particularly those needing multi-zone support where services span different clusters or clouds. The tool suits teams seeking a service mesh with a gradual learning curve and turnkey policies rather than low-level configuration. Kuma's multi-mesh capability allows multiple service meshes to coexist on the same control plane, supporting multi-tenancy patterns. Enterprise-level support is available for organizations requiring it.

The project receives almost all of its open issues from outside users rather than the core team, demonstrating a substantial base of real-world adopters. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker centers on feature requests, bug fixes, and improvements.