-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
BU Product Work
-
False
-
False
-
OCPSTRAT-62 - [B3-F7] Introduce Basic Observability for HyperShift
-
-
Hypershift Sprint 7
-
0
-
0
-
0
The control plane operator should automatically create service monitors for components that should have their metrics collected on the control plane of a Hypershift cluster. These include:
- Etcd
- Kube APIServer
- Kube ControllerManager
- OpenShift APIServer
- OpenShift ControllerManager
- OLM
- Networking (when OVN is updated to work on Hypershift)
- Cluster Version Operator
Initially the metrics excludes/includes should be similar to what is collected in a standalone hypershift cluster, but can eventually be optimized to only include metrics relevant to alerts required by the cluster provider.