Prometheus collects numerical measurements, such as request counts and response times, for monitoring and alerts. Maintaining several Prometheus installations and their lists of monitoring targets can become repetitive. Prometheus Operator lets teams describe instances and monitoring configuration as Kubernetes resources, then manages the corresponding deployments and configuration. This helps application teams expose services for monitoring through familiar labels and resource definitions. The operator is one component; the historical Helm chart of the same name became kube-prometheus-stack, a larger bundle. Identify which you operate before following upgrade instructions.
Current guidance
Prometheus Operator remains a project/component; the historical prometheus-operator Helm chart was renamed kube-prometheus-stack.
Determine whether the original deployment used the complete chart bundle or installed the operator separately. The correct upgrade notes depend on that identity. CRDs, selectors, custom monitors and persistent metrics need their own review.
After an upgrade, check target discovery and send a harmless test alert through the actual notification route. A healthy operator Pod does not prove that metrics and alerts still cover the intended workloads.
Historical upstream link check · 2026-10-09
The recorded upstream address redirects to https://github.com/prometheus-operator/prometheus-operator and returned HTTP 200 on 2026-10-09. GitHub does not mark prometheus-operator/prometheus-operator archived or disabled; this does not establish active maintenance, support or compatibility. GitHub resolves the old repository identity to prometheus-operator/prometheus-operator. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Original publication: 2018-09-28T05:00:16+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.
The Prometheus Operator for Kubernetes provides easy monitoring definitions for Kubernetes services and deployment and management of Prometheus instances.
Once installed, the Prometheus Operator provides the following features:
- Create/Destroy: Easily launch a Prometheus instance for your Kubernetes namespace, a specific application or team easily using the Operator.
- Simple Configuration: Configure the fundamentals of Prometheus like versions, persistence, retention policies, and replicas from a native Kubernetes resource.
- Target Services via Labels: Automatically generate monitoring target configurations based on familiar Kubernetes label queries; no need to learn a Prometheus specific configuration language.
For an introduction to the Prometheus Operator, see the initial blog post.
Prometheus Operator vs. kube-prometheus
The Prometheus Operator makes the Prometheus configuration Kubernetes native and manages and operates Prometheus and Alertmanager clusters. It is a piece of the puzzle regarding full end-to-end monitoring.
kube-prometheus combines the Prometheus Operator with a collection of manifests to help getting started with monitoring Kubernetes itself and applications running on top of it.
The post Prometheus Operator appeared first on kubedex.com.
Sources & further reading
Spotted something that needs another look?
Help improve this page →