Automatically generate monitoring target configurations based on familiar Kubernetes label queries; no need to learn a Prometheus specific configuration language.

The Prometheus resource declaratively describes the desired state of a Prometheus deployment, while ServiceMonitor and PodMonitor resources describe the targets to be monitored by Prometheus.

The easiest way of starting with the Prometheus Operator is by deploying it as part of kube-prometheus. kube-prometheus deploys the Prometheus Operator and already schedules a Prometheus called …

The Operator introduces custom resources like Prometheus, Alertmanager, ThanosRuler, and others, which help automate the deployment and configuration of these resources.

This guide assumes you already have a basic understanding of the Prometheus Operator and have gone through the Getting Started guide. We’re also expecting you to know how to run an …

Starting with prometheus-operator v0.65.x, one can use the ScrapeConfig CRD to scrape targets external to the Kubernetes cluster or create scrape configurations that are not possible with the …

This document describes the design and interaction between the custom resource definitions that the Prometheus Operator manages.

The Operator continuously reconciles the scrape and rules configuration and a sidecar container running in the Prometheus pods triggers a reload of the configuration when needed.

Mastodon Getting-Started Introduction Installing Prometheus Operator Compatibility Design API Reference

The Prometheus Operator works with PersistentVolumeClaims, which support the underlying PersistentVolume to be provisioned when requested. This document assumes a basic understanding …