-
Notifications
You must be signed in to change notification settings - Fork 73
Description
Hello,
We have an issue with Cluster Observability Operator, in particular when creating MonitoringStack.
For example when using this yaml:
apiVersion: monitoring.rhobs/v1alpha1
kind: MonitoringStack
metadata:
labels:
mso: test-prometheus
name: test-monitoring-stack
namespace: test-monitoring
spec:
alertmanagerConfig:
disabled: true
namespaceSelector:
matchExpressions:
- values:
- test-monitoring
key: kubernetes.io/metadata.name
operator: In
logLevel: debug
resourceSelector:
matchLabels:
app: test-metrics
retention: 1d
The Monitoring Stack is created and in Resources tab we can see:
"test-monitoring-stack-prometheus"
"test-monitoring-stack-prometheus-additional-scrape-configs"
"test-monitoring-stack-thanos-sidecar"
The problem is, that prometheus pods cannot start, because we get the following error:
"create Pod prometheus-test-monitoring-stack-0 in StatefulSet prometheus-test-monitoring-stack failed error: pods "prometheus-test-monitoring-stack-0" is forbidden: failed quota: test-monitoring-quota-compute-resources: must specify limits.cpu for: thanos-sidecar; limits.memory for: thanos-sidecar; requests.cpu for: thanos-sidecar; requests.memory for: thanos-sidecar"
We cannot find any documentation/instructions/guide on how to setup the limits for thanos-sidecar, because changing "resources" in the monitoringstack yaml only changes the limits for PROMETHEUS pods, but not thanos-sidecar.
Additionally, in our case we don't even need thanos-sidecar and would like to disable it completely like we can disable "alertmanager".
Thank you!