prometheus-operator/prometheus-operator

Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 18 minutes ago
Added to GitGenius on March 17th, 2026
Created on September 22nd, 2016
Open Issues & Pull Requests: 297 (+0)
Number of forks: 3,867
Total Stargazers: 9,973 (+0)
Total Subscribers: 137 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.1 hours
Mean response time: 263.8 days
90th percentile: 1221.2 days
Tracked items: 596

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 92% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "area/testing" is answered fastest, typically in about 4 hours, while "kind/documentation" waits about 31 hours. 70% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 152
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 688 days
Stale 30+ days: 144
Stale 90+ days: 136

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 6
Events in 7 days: 22

Top labels

  • kind/feature (276)
  • help wanted (181)
  • kind/support (120)
  • kind/bug (112)
  • stale (90)
  • kind/enhancement (66)
  • kind/documentation (53)
  • good first issue (51)

Detailed Description

The Prometheus Operator is a Kubernetes-native tool that automates the deployment and management of Prometheus monitoring clusters and related components. Written in Go, it extends Kubernetes functionality through custom resources, allowing operators to define and manage Prometheus, Alertmanager, and other monitoring tools declaratively using familiar Kubernetes APIs rather than learning Prometheus-specific configuration languages.

The project operates through a set of Custom Resource Definitions that the operator monitors for changes and synchronizes with actual deployments. These include Prometheus for defining Prometheus deployments, PrometheusAgent for agent-mode deployments, Alertmanager for alert management, ThanosRuler for distributed rule evaluation, ServiceMonitor and PodMonitor for declarative service and pod monitoring, Probe for ingress and static target monitoring, ScrapeConfig for external resource scraping, PrometheusRule for alerting and recording rules, and AlertmanagerConfig for alert routing configuration. The operator automatically generates appropriate scrape configurations based on Kubernetes label queries, eliminating manual configuration overhead.

The operator includes dynamic admission control through a webhook that validates PrometheusRule resources before deployment, preventing invalid alerting and recording rules from breaking Prometheus instances. Core features enable simplified deployment configuration where users can manage Prometheus versions, persistence, retention policies, and replicas through native Kubernetes resources. The project distinguishes itself from related offerings like kube-prometheus, which provides complete stack examples, and the prometheus-community Helm chart, which offers similar functionality through Helm packaging.

The operator is classified as production-ready, with stable v1 CRDs providing backward-compatible APIs. The v1beta1 CRDs are considered unstable but suitable for production use by those accepting breaking change risks, while v1alpha1 CRDs are experimental. The project requires Kubernetes version 1.16.0 or later and recommends using the latest stable release for new deployments.

The project maintains comprehensive documentation including getting started guides, design documentation, user guides for webhook functionality, and troubleshooting resources. It includes explicit security reporting procedures directing vulnerability disclosures to maintainers rather than public issue tracking, and maintains an AI usage policy for contributors.