Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-1063

MonitoringStack doesn't set default resource requests and limits on Alertmanager and thanos component in Prometheus

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • monitoring-stack
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 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

              Unassigned Unassigned
              rhn-support-alosingh Alok Singh
              None
              None
              None
              Hongyan Li Hongyan Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: