Persistent Storage & Metric Retention in Kube-Prometheus-Stack (2026)
Configure persistent volumes for Prometheus and Grafana in kube-prometheus-stack, tune retention size versus retention time, and reuse an existing PVC safely.
Read Article Topic
Kube-Prometheus-Stack Configuration Guides
The default install of kube-prometheus-stack is a reasonable starting point, but almost every team ends up customizing it — adjusting Prometheus retention, enabling persistent storage for Grafana, tuning resource requests, or wiring Alertmanager to a real notification channel. All of that customization flows through one file: values.yaml.
This category collects everything related to tuning the chart after installation: what each major values.yaml section controls, which defaults are safe to keep, and which ones you should almost always override before going to production.
Kube-Prometheus-Stack values.yaml: Every Configuration Option Explained (2026)
The definitive guide to kube-prometheus-stack values.yaml configuration. Prometheus retention, Grafana persistence, Alertmanager routing, resource limits, and production-ready settings.
Read ArticleKube-Prometheus-Stack Helm Chart Documentation: The Complete 2026 Guide
The most complete kube-prometheus-stack Helm chart documentation for 2026. Installation, values.yaml configuration, CRDs, upgrading, production best practices — everything in one place.
Read ArticleFrequently Asked Questions
What is the single most important values.yaml setting to review before production?
Persistent storage for Prometheus and Grafana — without it, all metric history and custom dashboards are lost on every pod restart, which is the single most common first production mistake.
Can kube-prometheus-stack be configured without editing values.yaml directly?
Not really — values.yaml is the chart's only configuration surface. There is no separate UI or CLI for chart-level settings, though individual components like Grafana do have their own runtime settings.