-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
When creating MonitoringStack in COO, the Alertmanager object and thanos component inside Pormetheus object don't get the resource requests and limits by default.
This is an issue. When resourcequota is set on the namespace where MonitoringStack is created, the pods for Alertmanager and Prometheus fail to start with errors like below.
create Pod alertmanager-example-hack-monitoring-stack-0 in StatefulSet alertmanager-example-hack-monitoring-stack failed error: pods "alertmanager-example-hack-monitoring-stack-0" is forbidden: failed quota: namespace-quota: must specify limits.cpu for: alertmanager; limits.memory for: alertmanager; requests.cpu for: alertmanager
create Pod prometheus-example-hack-monitoring-stack-0 in StatefulSet prometheus-example-hack-monitoring-stack failed error: pods "prometheus-example-hack-monitoring-stack-0" is forbidden: failed quota: namespace-quota: must specify limits.cpu for: thanos-sidecar; limits.memory for: thanos-sidecar; requests.cpu for: thanos-sidecar; requests.memory for: thanos-sidecar