Prometheus Operator CRDs

A Helm chart that collects custom resource definitions (CRDs) from the Prometheus Operator, allowing for seamless integration with GitOps tools

  • Infrastructure
  • Monitoring & Logging
A Helm chart that collects custom resource definitions (CRDs) from the Prometheus Operator, allowing for seamless integration with GitOps tools

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 17 days ago
Popular
809,993 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
9,993
Open issues
297
Last commit
2026-11-04
Latest release
v0.94.2
License
Apache-2.0
Activity
steady

Checked 17 days ago - source: GitHub (prometheus-operator/prometheus-operator)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Start Prometheus with your config file Run ./prometheus --config.file=prometheus.yml from the folder with your config, then open http://localhost:9090 to confirm it started. Without that config file, Prometheus does not know what to collect, and the ./data folder holds its database, so keep that folder safe. source
  • Start the example Node Exporter targets If you are following the example, unpack Node Exporter (the tool that reports a server's metrics) and start three copies in separate command windows on ports 8080, 8081, and 8082. Those ports are where Prometheus reads a /metrics page, so the example data will not appear unless those copies are running. source

Fetched 46 days ago - each note links to its source

Alternatives (12)

  • Amazon CloudWatch - Amazon CloudWatch is a monitoring service for AWS cloud resources and the applications running on AWS.
  • Better Stack - AI-driven monitoring platform providing incident management, real-time logs, uptime, traces, error tracking, infrastructure analytics, and…
  • Datadog - Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
  • DeepFlow - Unify your cloud-native monitoring with zero-code eBPF, advanced profiling, and 10x storage efficiency.
  • Grafana Loki - Grafana Loki is an open-source log aggregation system.
  • Graylog - Graylog is a centralized log management platform built on open standards for capturing, storing, and analyzing terabytes of machine data in…
  • InfluxDB - InfluxDB is an open source time series database with no external dependencies.
  • Kibana - Kibana is the data visualization layer for querying, analyzing, and managing data stored in Elasticsearch.
  • New Relic - Pinpoint and solve performance issues in your Ruby, Java, .NET, PHP and Python apps with real user, application and server monitoring.
  • Prometheus - Prometheus is a systems and service monitoring system.
  • Splunk - Splunk is a self-hosted platform for collecting, indexing, searching, and analyzing log and security data, helping homelabbers and operatio…
  • VictoriaMetrics - VictoriaMetrics is a fast, cost-effective, and scalable open-source time-series database that stores long-term monitoring metrics, accepts…

Checked 40 days ago - source: AlternativeTo

Common questions

Do I need to update the CRDs before upgrading kube-prometheus-stack?

Yes, run the CRD update commands before applying the upgrade.

Which fields determine which scrape configurations the Operator includes?

The Prometheus and PrometheusAgent CRDs use podMonitorSelector, serviceMonitorSelector, probeSelector, and scrapeConfigSelector to determine which ServiceMonitor, PodMonitor, Probe, and ScrapeConfig resources are included for scraping.

What does the Operator do when Kubernetes objects change?

It monitors the Kubernetes API server for changes to specific objects and ensures the current Prometheus deployments match them. It acts on CRDs such as Prometheus.

Where is the Prometheus database stored for backups?

The ./data folder holds the Prometheus database, so keep that folder safe if you need to back it up.

Does the Operator also manage Alertmanager?

Yes, the Operator makes Prometheus configuration Kubernetes-native and manages Prometheus and Alertmanager clusters.

Answers sourced from github.com, github.com, github.com, stackoverflow.com, www.reddit.com

Community

Collected 48 days ago - public community threads