Alert[0]: deployment_validation_operator_unset_cpu_requirements Validation error for notifications: Indicates when containers do not have CPU requests and limits set.

Annotations:

• dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=notifications-stage
• html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
• runbook = Set CPU requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.

Labels:

• alertname = deployment_validation_operator_unset_cpu_requirements
• app = notifications
• check_description = Indicates when containers do not have CPU requests and limits set.
• check_remediation = Set CPU requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
• cluster = crcs02ue1
• endpoint = http-metrics
• environment = staging
• exported_namespace = notifications-stage
• instance = 10.131.4.70:8383
• jiralert = NOTIF
• job = deployment-validation-operator-metrics
• kind = Job
• name = notifications-do-nothing-job-ff31fd3-64ca21e
• namespace = deployment-validation-operator
• pod = deployment-validation-operator-6cbcbbbfd5-g95qh
• prometheus = openshift-customer-monitoring/app-sre
• service = deployment-validation-operator
• severity = medium

Source: Prometheus

Alert[1]: deployment_validation_operator_unset_cpu_requirements Validation error for notifications: Indicates when containers do not have CPU requests and limits set.

Annotations:

• dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=notifications-stage
• html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
• runbook = Set CPU requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.

Labels:

• alertname = deployment_validation_operator_unset_cpu_requirements
• app = notifications
• check_description = Indicates when containers do not have CPU requests and limits set.
• check_remediation = Set CPU requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
• cluster = crcs02ue1
• endpoint = http-metrics
• environment = staging
• exported_namespace = notifications-stage
• instance = 10.131.4.70:8383
• jiralert = NOTIF
• job = deployment-validation-operator-metrics
• kind = Job
• name = notifications-do-nothing-job-ff31fd3-e5463b1
• namespace = deployment-validation-operator
• pod = deployment-validation-operator-6cbcbbbfd5-g95qh
• prometheus = openshift-customer-monitoring/app-sre
• service = deployment-validation-operator
• severity = medium

Source: Prometheus

Note: This issue was generated automatically by the AppSRE team. Moving this issue to a different project will result in the ticket being recreated in the current project. If you believe that this issue was created in the incorrect project, please reach out to AppSRE.