zalando/postgres-operator

Postgres operator creates and manages PostgreSQL clusters running in Kubernetes

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

zalando/postgres-operator has 5k+ stars and 1k+ forks on GitHub, is written in Go, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 13th, 2026
Created on May 12th, 2017
Open Issues & Pull Requests: 548 (+0)
GitHub issues: Enabled
Number of forks: 1,074
Total Stargazers: 5,255 (+0)
Total Subscribers: 59 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.6 days
Mean response time: 179.0 days
90th percentile: 477.0 days
Tracked items: 423

Maintainer activity

1 person 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 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

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 "technical issue" is answered fastest, typically in about 2 days, while "idea" waits about 3 weeks. Only 39% of issues opened in the past year have been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 180
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 901 days
Stale 30+ days: 171
Stale 90+ days: 151

Recent activity

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

Top labels

  • question (74)
  • enhancement (45)
  • help wanted (28)
  • good first issue (24)
  • spilo (19)
  • discussion (17)
  • bug (14)
  • idea (12)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Postgres Operator is a Kubernetes operator that creates and manages highly available PostgreSQL clusters running on Kubernetes.

The operator solves the problem of running production PostgreSQL on Kubernetes by automating cluster lifecycle management through Kubernetes Custom Resource Definitions. Rather than requiring direct Kubernetes API access, administrators define PostgreSQL clusters declaratively using manifests, enabling infrastructure-as-code workflows and CI/CD integration. The operator leverages Patroni to handle streaming replication and high availability, while providing features like rolling updates, live volume resizing, connection pooling via PGBouncer, and point-in-time recovery using pg_basebackup or WAL-G.

Teams should adopt this tool if they run PostgreSQL workloads on Kubernetes and want automated cluster provisioning and management without manual operations. It suits organizations already using Kubernetes who need production-grade PostgreSQL with high availability and want to avoid managing database infrastructure directly. The operator supports major version upgrades across all clusters, restore and cloning across AWS, GCS, and Azure, and standby clusters from remote WAL archives. It works in non-cloud environments and is compatible with OpenShift. The tool includes a UI for creating and editing cluster manifests, basic credential and user management, custom TLS certificate support, and multi-architecture deployments.

The project maintains active test coverage with both unit and end-to-end test workflows. Development activity shows consistent engagement with the codebase through regular updates and maintenance of compatibility across supported PostgreSQL versions.