# Prometheus Operator

Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes

Repository: https://github.com/prometheus-operator/prometheus-operator
Canonical: https://ross.abutalabs.com/products/prometheus-operator
Homepage: https://prometheus-operator.dev
Language: Go
License: Apache-2.0
License Family: permissive
Topics: kubernetes, prometheus, monitoring, hacktoberfest
Last push: 2026-08-25T12:42:47+00:00
Link (homepage): https://prometheus-operator.dev
Link (site_page): https://prometheus-operator.dev/docs/getting-started/introduction

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 97, longevity 100
- inputs: {"age_days": 3632, "days_push": 8, "days_rel": 23, "gap_med": 17, "n_releases_24m": 36}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 9975, forks 3867 (observed 2026-08-28T04:10:39.132973+00:00)

## What it is
A Kubernetes operator that provides Kubernetes-native deployment and management of Prometheus, Alertmanager, and related monitoring components via custom resource definitions. It automates configuration of Prometheus monitoring stacks, generating scrape targets from Kubernetes label selectors instead of hand-written Prometheus configuration.

## Use cases
- deploy prometheus on kubernetes
- manage alertmanager with kubernetes custom resources
- auto-discover monitoring targets from kubernetes labels
- set up a complete cluster monitoring stack
- configure prometheus rules and alerts declaratively
- run thanos ruler on kubernetes

## When to choose
- you run workloads on Kubernetes and want a Prometheus-based monitoring stack managed declaratively
- you want automatic service discovery and scrape configuration via ServiceMonitor/PodMonitor resources
- you want a production-ready, community-standard way to operate Prometheus and Alertmanager

## When to avoid
- you are not running Kubernetes - use plain Prometheus instead
- you need a lightweight monitoring setup without operator overhead
- you rely on v1alpha1 CRDs for mission-critical environments, as that API is unstable

## Facets
- artifact type: infra-config
- maturity: stable
- function: monitoring, alerting, deployment, container-orchestration
- domain: monitoring, cloud-computing
- platform: go, self-hosted
- tags: prometheus, kubernetes-operator, alertmanager, crds, observability, kube-prometheus, servicemonitor, devops, containers, kubernetes, docker

## Member repositories
- prometheus-operator/prometheus-operator (main) score 98
- prometheus-operator/kube-prometheus (infra) score 87

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:39.132973+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:20:02.881444+00:00, confidence not recorded.
  - readme: https://github.com/prometheus-operator/prometheus-operator (fetched 2026-08-28T04:10:39.132973+00:00, sha 4977ea6aa076)
  - homepage: https://prometheus-operator.dev (fetched 2026-08-29T08:19:52.595903+00:00, sha e043217f241d)
  - site_page: https://prometheus-operator.dev/docs/getting-started/introduction (fetched 2026-08-29T08:19:52.604931+00:00, sha 5314589ea68c)
- Data as of 2026-08-30T08:39:29.467469+00:00.