kube-prometheus-stack installs a collection of monitoring components configured for Kubernetes, built around Prometheus and Prometheus Operator. It helps teams start collecting cluster measurements, applying monitoring rules and connecting the dashboards and alerting pieces of that system. It is useful when a coordinated monitoring package fits better than assembling each component separately. The package also owns shared configuration and persistent history, so replacing a release requires checking more than whether the new Pods start.
Deployment and operating notes
The prometheus-community kube-prometheus-stack chart packages Prometheus Operator with a Kubernetes monitoring configuration and related components. It is the chart lineage to investigate when an old installation refers to the retired stable/prometheus-operator chart. The chart rename did not retire Prometheus Operator itself.
Why upgrades need planning
Cluster-scoped CRDs, release names, selectors, dashboards, alert rules and persistent storage can all outlive an individual Helm command. Inspect the upgrade notes for each crossed chart major and identify who owns CRD changes. A fresh successful install does not validate the migration of an existing monitoring estate.
Acceptance criteria
Compare discovered targets, rule evaluations, recording series, alert delivery and dashboards before deleting the old stack. Confirm that retained time series remain available for the required retention period. Test an actual notification through the configured receiver rather than treating a healthy Alertmanager pod as delivery evidence.
See the migration guide for an inventory and cutover sequence.
Sources & further reading
Spotted something that needs another look?
Help improve this page →