-
Task
-
Resolution: Done
-
Blocker
-
None
-
None
-
- JIRALERT{a33a987fcf992fd1f0609dc65665359a39d961ad199457816ffcf7323762835f1c5967505ab2c07e4228ecf4b34db6cb59077d32976b7b1a4fab1ad88ac70269}
- alertname="deployment_validation_operator_default_service_account"
- app="notifications"
- cluster="crcp01ue1"
- job="deployment-validation-operator-metrics"
- platform-notifications
- service="deployment-validation-operator"
-
False
-
-
False
-
None
Alert: deployment_validation_operator_default_service_account Validation error for notifications: 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=crcp01ue1&var-namespace=notifications-prod
- 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 = notifications
- 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 = crcp01ue1
- endpoint = http-metrics
- environment = production
- exported_namespace = notifications-prod
- instance = 10.130.12.11:8383
- jiralert = NOTIF
- job = deployment-validation-operator-metrics
- kind = CronJob
- name = notifications-db-cleaner-cronjob
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-6cbcbbbfd5-cjhrk
- 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.