Alert: deployment_validation_operator_no_readiness_probe Validation error for Cincinnati: Indicates when containers fail to specify a readiness probe.

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=cincinnati-stage
• html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-no_readiness_probe.yaml.j2
• runbook = Specify a readiness probe in your container. Refer to https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ for details.

Labels:

• alertname = deployment_validation_operator_no_readiness_probe
• app = Cincinnati
• check_description = Indicates when containers fail to specify a readiness probe.
• check_remediation = Specify a readiness probe in your container. Refer to https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ for details.
• cluster = app-sre-stage-01
• endpoint = http-metrics
• environment = staging
• exported_namespace = cincinnati-stage
• instance = 10.128.14.28:8383
• jiralert = OTA
• job = deployment-validation-operator-metrics
• kind = StatefulSet
• name = nginx-proxy-cache
• namespace = deployment-validation-operator
• pod = deployment-validation-operator-6cbcbbbfd5-fwk8j
• 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.