-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
4.13
-
False
-
None
-
False
-
-
-
Workloads Sprint 230, Workloads Sprint 231, Workloads Sprint 232, Workloads Sprint 233, Workloads Sprint 234, Workloads Sprint 235, Workloads Sprint 236, Workloads Sprint 237, Workloads Sprint 238, Workloads Sprint 239, Workloads Sprint 240, Workloads Sprint 241
The current implementation of the [CRQ controller](https://github.com/openshift/cluster-policy-controller/blob/f1fe7bf5a097fb85a05d6ed61f4eedea9e71077b/pkg/quota/clusterquotareconciliation/reconciliation_controller.go#L165) does not sufficiently reports whether discovered resources are empty or whether the CRQ controller is reconciling properly. For that, we need metrics that will reflect whether:
- resource discovery returns valid data (e.g. returning empty list of resources with empty error is sign of something incorrect happening)
- CRQ controller is properly reconciling all CRQ objects. E.g. every object is expected to be forcefully updated every 5 minutes by default. Metrics might report the last time any CRQ object was successfully updated.
- other indication of correct/incorrect behavior
This will require analysis of the code to detect the right spots for recording. The KCM operator might be extended to report whether the CRQ controller degraded or not manifesting suspicious activity.
- relates to
-
WRKLDS-358 Expose additional information about GC and Quota under /debug endpoint
- To Do