Alert[0]: deployment_validation_operator_unset_cpu_requirements Validation error for service-registry: 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=app-sre-stage-01&var-namespace=service-registry-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 = service-registry
• 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 = app-sre-stage-01
• endpoint = http-metrics
• environment = staging
• exported_namespace = service-registry-stage
• instance = 10.130.28.24:8383
• jiralert = MGDSR
• job = deployment-validation-operator-metrics
• kind = CronJob
• name = fleet-manager-instances-list-stage
• namespace = openshift-deployment-validation-operator
• namespace_uid = 9926ece4-f9e4-4759-8158-aa6440caf889
• pod = deployment-validation-operator-699c4fdb59-tt8hh
• prometheus = openshift-customer-monitoring/app-sre
• service = deployment-validation-operator
• severity = medium
• uid = 3e80dc25-3317-4b36-a03d-c4e55cf559c2

Source: Prometheus

Alert[1]: deployment_validation_operator_unset_cpu_requirements Validation error for service-registry: 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=app-sre-stage-01&var-namespace=service-registry-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 = service-registry
• 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 = app-sre-stage-01
• endpoint = http-metrics
• environment = staging
• exported_namespace = service-registry-stage
• instance = 10.130.28.24:8383
• jiralert = MGDSR
• job = deployment-validation-operator-metrics
• kind = Job
• name = apicurio-perf-e2e-e1f4494
• namespace = openshift-deployment-validation-operator
• namespace_uid = 9926ece4-f9e4-4759-8158-aa6440caf889
• pod = deployment-validation-operator-699c4fdb59-tt8hh
• prometheus = openshift-customer-monitoring/app-sre
• service = deployment-validation-operator
• severity = medium
• uid = 0ae6e06b-2e31-41e7-bebe-7a4d218f6013

Source: Prometheus

Alert[2]: deployment_validation_operator_unset_cpu_requirements Validation error for service-registry: 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=app-sre-stage-01&var-namespace=service-registry-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 = service-registry
• 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 = app-sre-stage-01
• endpoint = http-metrics
• environment = staging
• exported_namespace = service-registry-stage
• instance = 10.130.28.24:8383
• jiralert = MGDSR
• job = deployment-validation-operator-metrics
• kind = Job
• name = service-registry-instance-list
• namespace = openshift-deployment-validation-operator
• namespace_uid = 9926ece4-f9e4-4759-8158-aa6440caf889
• pod = deployment-validation-operator-699c4fdb59-tt8hh
• prometheus = openshift-customer-monitoring/app-sre
• service = deployment-validation-operator
• severity = medium
• uid = e01a9203-7a72-401e-8ff3-c6451e272e1c

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.