-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
- JIRALERT{34a010536703835eac7ccd6ea9ba979b042e691731f65454c7d4dc0613aa94bed2b48c183d5f8c1d5d71e0eb7a958306cf5399c83d58d4cea1d12bea559fa67f}
- alertname="deployment_validation_operator_latest_tag"
- app="playbook-dispatcher"
- cluster="crcs02ue1"
- job="deployment-validation-operator-metrics"
- platform-integrations
- service="deployment-validation-operator"
-
False
-
-
False
-
Unset
-
None
Alert: deployment_validation_operator_latest_tag Validation error for playbook-dispatcher: Indicates when a deployment-like object is running a container with an invalid container image
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=playbook-dispatcher-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-latest_tag.yaml.j2
- runbook = Use a container image with a proper image tag satisfying either the "AllowList" & "BlockList" regex patterns.
Labels:
- alertname = deployment_validation_operator_latest_tag
- app = playbook-dispatcher
- check_description = Indicates when a deployment-like object is running a container with an invalid container image
- check_remediation = Use a container image with a proper image tag satisfying either the "AllowList" & "BlockList" regex patterns.
- cluster = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = playbook-dispatcher-stage
- instance = 10.130.4.34:8383
- jiralert = RHCLOUD
- job = deployment-validation-operator-metrics
- kind = Job
- name = playbook-dispatcher-org-id-populator-jb75eri
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-6cbcbbbfd5-gwxrc
- 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.