In Cluster Observability Operator unable to configure resource requests and limits for ThanosQuerier component in RHOCP4
Issue
-
When deploying the Cluster Observability Operator, the
ThanosQueriercomponent fails to start in namespaces where resource governance policies are enforced. -
The
ThanosQuerierpods are created without CPU and memoryrequests or limits, and the operator does not provide a supported way to configure these values. -
As a result, pod creation is blocked by the admission controller.
Environment
- Red Hat OpenShift Container Platform
- 4
- Cluster Observability Operator (COO)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
