# Prometheus Operator — Kubernetes-Native Monitoring Stack Management

> Prometheus Operator simplifies deploying and managing Prometheus, Alertmanager, and related monitoring components on Kubernetes using custom resources and reconciliation loops.

## Install

Save as a script file and run:

# Prometheus Operator — Kubernetes-Native Monitoring Stack Management

## Quick Use
```bash
# Install via kube-prometheus-stack Helm chart (recommended)
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm install kube-prom prometheus-community/kube-prometheus-stack -n monitoring --create-namespace

# Define a ServiceMonitor to scrape your app
kubectl apply -f - <<EOF
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: my-app
spec:
  selector:
    matchLabels:
      app: my-app
  endpoints:
  - port: metrics
EOF
```

## Introduction
Prometheus Operator introduces Kubernetes custom resources — Prometheus, Alertmanager, ServiceMonitor, PodMonitor, and PrometheusRule — to declaratively manage the entire monitoring stack. Instead of editing Prometheus config files manually, you define monitoring targets and alert rules as Kubernetes objects that the operator reconciles automatically.

## What Prometheus Operator Does
- Deploys and manages Prometheus server instances as StatefulSets via CRDs
- Auto-discovers scrape targets through ServiceMonitor and PodMonitor resources
- Manages Alertmanager clusters with routing and receiver configuration as code
- Reconciles PrometheusRule resources into Prometheus recording and alerting rules
- Handles Prometheus version upgrades, scaling, and persistent storage automatically

## Architecture Overview
The operator runs as a Deployment that watches for Prometheus, Alertmanager, ServiceMonitor, PodMonitor, and PrometheusRule custom resources. When a ServiceMonitor is created, the operator generates the corresponding scrape configuration and injects it into the Prometheus StatefulSet via a mounted ConfigMap or Secret. Prometheus instances discover targets dynamically without restarts. The operator also manages TLS certificates and RBAC for each Prometheus instance.

## Self-Hosting & Configuration
- Deploy via the kube-prometheus-stack Helm chart for a batteries-included setup with Grafana
- Or install the operator standalone with `kubectl apply -f bundle.yaml` from GitHub releases
- Create Prometheus CRs to define instance count, retention, and storage class
- Use ServiceMonitor `namespaceSelector` to scope which namespaces are scraped
- Configure Alertmanager CRs with Slack, PagerDuty, or webhook receivers

## Key Features
- Declarative monitoring: all configuration lives in version-controlled Kubernetes manifests
- Auto-discovery of scrape targets via label selectors on ServiceMonitor/PodMonitor
- High availability with built-in support for Prometheus and Alertmanager clustering
- Thanos sidecar integration for long-term storage and global querying
- Comprehensive kube-prometheus-stack bundles Grafana dashboards, node-exporter, and kube-state-metrics

## Comparison with Similar Tools
- **Vanilla Prometheus** — requires hand-crafted config files and manual target management
- **Victoria Metrics Operator** — similar CRD approach but tied to VictoriaMetrics backend
- **Datadog/New Relic** — managed SaaS monitoring with per-host pricing vs self-hosted open source
- **Grafana Agent/Alloy** — lightweight collector that can replace Prometheus but lacks the CRD workflow
- **Thanos** — complements Prometheus Operator for global view and long-term storage

## FAQ
**Q: Do I need the operator to run Prometheus on Kubernetes?**
A: No, but the operator dramatically simplifies configuration, upgrades, and target discovery compared to managing Prometheus manually.

**Q: Can I run multiple Prometheus instances?**
A: Yes. Create multiple Prometheus CRs, each scoped to different namespaces or label selectors for workload isolation.

**Q: How do I add alerting rules?**
A: Create PrometheusRule resources with your PromQL expressions. The operator injects them into the matching Prometheus instance automatically.

**Q: Does it work with managed Kubernetes (EKS, GKE, AKS)?**
A: Yes. The operator works on any conformant Kubernetes cluster regardless of provider.

## Sources
- https://github.com/prometheus-operator/prometheus-operator
- https://prometheus-operator.dev/docs/

---
Source: https://tokrepo.com/en/workflows/064a2633-3943-11f1-9bc6-00163e2b0d79
Author: Script Depot