-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
- JIRALERT{5062ae034f3542109e219c7c88c682ff228cb34fbea5e14d0ba34dfb21446ef874479922a229b3c39885b5de4761a8a21f07284caaa81f146a4908eff9823b84}
- alertname="deployment_validation_operator_default_service_account"
- app="module-update-router"
- cluster="crcs02ue1"
- job="deployment-validation-operator-metrics"
- service="deployment-validation-operator"
-
False
-
-
False
-
Unset
Alert: deployment_validation_operator_default_service_account Validation error for module-update-router: Indicates when pods use the default service account.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=module-update-router-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-default_service_account.yaml.j2
- runbook = Create a dedicated service account for your pod. Refer to https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/ for details.
Labels:
- alertname = deployment_validation_operator_default_service_account
- app = module-update-router
- check_description = Indicates when pods use the default service account.
- check_remediation = Create a dedicated service account for your pod. Refer to https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/ for details.
- cluster = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = module-update-router-stage
- instance = 10.130.2.37:8383
- jiralert = RHCLOUD
- job = deployment-validation-operator-metrics
- kind = Deployment
- name = module-update-router
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-6cbcbbbfd5-xx4hr
- 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.