apecloud/kubeblocks

KubeBlocks is a Kubernetes Operator designed to manage a variety of databases and streaming systems, including MySQL, PostgreSQL, MongoDB, Redis, RabbitMQ,...

View on GitHub ↗Jump to charts ↓Open shareable report →

apecloud/kubeblocks has 3k+ stars and 250+ forks on GitHub, is written in Go, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 22nd, 2026
Created on August 22nd, 2022
Open Issues & Pull Requests: 254 (+0)
GitHub issues: Enabled
Number of forks: 283
Total Stargazers: 3,149 (+0)
Total Subscribers: 23 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 13.5 hours
90th percentile: 0.9 hours
Tracked items: 1,362

Maintainer activity

17 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 13% of issues opened in the past year have never received a reply. 74% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 57% of tracked open issues have had no activity in three months. 68% of issues opened in the past year have been closed, leaving a working backlog. Three people close 53% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 187
New in 7 days: 9
Closed in 7 days: 8
Avg open age: 246 days
Stale 30+ days: 174
Stale 90+ days: 130

Recent activity

Opened in 7 days: 6
Closed in 7 days: 6
Comments in 7 days: 0
Events in 7 days: 8

Top labels

  • kind/bug (958)
  • Stale (298)
  • kind/enhancement (155)
  • kind/feature (99)
  • severity/major (72)
  • bug (57)
  • documentation (49)
  • area/user-interaction (45)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

KubeBlocks is a Kubernetes Operator that manages multiple database and streaming systems including MySQL, PostgreSQL, MongoDB, Redis, RabbitMQ, and RocketMQ within Kubernetes environments.

The operator addresses the complexity of running stateful database workloads on Kubernetes by providing unified management across diverse database engines. Rather than requiring separate operators for each database type, KubeBlocks consolidates database lifecycle operations—provisioning, scaling, backup, and failover—under a single operator framework. This approach reduces operational overhead and standardizes how teams interact with different database systems running in their clusters.

Teams should adopt KubeBlocks if they run multiple database engines on Kubernetes and want to avoid managing separate operators for each one. It suits organizations that need consistent operational patterns across heterogeneous database deployments and prefer a single control plane for database infrastructure. The tool is particularly valuable for teams managing both relational databases like MySQL and PostgreSQL alongside NoSQL systems like MongoDB and Redis, or message brokers like RabbitMQ and RocketMQ.

The project shows active development with regular commits across its codebase and consistent engagement with issues and pull requests. The maintainers respond to community contributions and maintain documentation alongside code changes. Development activity indicates ongoing refinement of operator capabilities and expansion of supported database engines.