Chapter 6. Installing Red Hat OpenShift 3.11 on IBM PowerVC 143
Figure 6-5   OpenShift monitoring
As highlighted in Figure 6-5, at the heart of the monitoring stack sits the OpenShift Container 
Platform Cluster Monitoring Operator (CMO), which watches over the deployed monitoring 
components and resources and ensures that these are always up-to-date.
The Prometheus Operator (PO) creates, configures, and manages Prometheus and 
Alertmanager instances. It also automatically generates monitoring target configurations 
based on familiar Kubernetes label queries.
In addition to Prometheus and Alertmanager, OpenShift Container Platform Monitoring 
includes node-exporter and kube-state-metrics. Node-exporter is an agent that is deployed 
on every node to collect metrics about it. The kube-state-metrics exporter agent converts 
Kubernetes objects to metrics consumable by Prometheus.
The following targets are monitored as part of the cluster monitoring:
/SM590000Prometheus itself
/SM590000Prometheus-Operator
/SM590000cluster-monitoring-operator
/SM590000Alertmanager cluster instances
/SM590000Kubernetes apiserver
/SM590000kubelets (the kubelet embeds cAdvisor for per container metrics)
/SM590000kube-controllers
/SM590000kube-state-metrics
/SM590000node-exporter
/SM590000etcd (if etcd monitoring is enabled)
All of these components are automatically updated. For more information about the OpenShift 
Container Platform Cluster Monitoring Operator, see this web page.
Configuring OpenShift Container Platform cluster monitoring
The OpenShift Cluster Monitoring is deployed by Ansible Playbooks. You can choose the 
base playbook or the openshift-monitoring playbook for the deployment.