cloudnative-pg/charts

Official Helm charts for the operator, database clusters and the Barman Cloud plugin.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

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

cloudnative-pg/charts has 600+ stars and 250+ forks on GitHub, is written in Go Template, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on October 15th, 2026
Created on April 21st, 2022
Open Issues & Pull Requests: 128 (+0)
GitHub issues: Enabled
Number of forks: 269
Total Stargazers: 632 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.9 days
Mean response time: 46.8 days
90th percentile: 104.6 days
Tracked items: 202

Maintainer activity

5 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

Roughly one issue in three opened in the past year never receives 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 "bug" is answered fastest, typically in about 13 hours, while "chart( operator )" waits about 5 weeks. 38% of tracked open issues have had no activity in three months. 62% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 54
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 144 days
Stale 30+ days: 33
Stale 90+ days: 16

Recent activity

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

Top labels

  • chart( cluster ) (134)
  • bug (53)
  • chart( operator ) (52)
  • chart( plugin-barman-cloud ) (18)
  • dependencies (4)
  • release (2)
  • stale (2)
  • breaking changes (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

CloudNativePG Helm Charts is a collection of Helm charts for deploying and managing PostgreSQL workloads on Kubernetes. The project provides three distinct charts: one for installing the CloudNativePG operator itself, one for deploying PostgreSQL database clusters managed by that operator, and one for the Barman Cloud plugin that handles backup and recovery operations. Together, these charts enable operators to manage PostgreSQL across private, public, or hybrid cloud environments using Kubernetes-native tooling.

The charts solve the problem of standardizing and simplifying PostgreSQL deployment on Kubernetes by packaging the operator, cluster configuration, and backup tooling into reusable Helm templates. Rather than manually configuring Kubernetes resources, users can leverage these charts to quickly provision the operator, spin up database clusters with declarative configuration, and integrate backup capabilities through the Barman Cloud plugin. Each chart includes comprehensive documentation covering installation and advanced configuration options specific to its purpose.

Teams running PostgreSQL on Kubernetes should adopt these charts if they want an officially maintained, operator-backed approach to cluster management. The charts suit organizations already committed to the CloudNativePG ecosystem and those seeking a Kubernetes-native alternative to traditional PostgreSQL administration. The operator chart supports only the latest point release of CloudNativePG, so users must keep their operator version current to remain compatible.

The project maintains active contribution guidelines and a code of conduct, indicating structured community engagement. Development activity shows consistent attention to keeping the charts aligned with the latest operator releases, reflecting a commitment to supporting current versions rather than maintaining backward compatibility across multiple operator generations.