-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
- JIRALERT{675c8adb1d43782b8b138f64dd221b91a973e62d32de557c0772cfd567bf578220703635daec8ed469c22ee7fb5ca407ce42e455afa1cc897805c25a46cad940}
- alertname="deployment_validation_operator_default_service_account"
- app="payload-tracker"
- cluster="crcp01ue1"
- job="deployment-validation-operator-metrics"
- platform-integrations
- platform-pipeline
- service="deployment-validation-operator"
Alert: deployment_validation_operator_default_service_account Validation error for payload-tracker: 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=payload-tracker-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 = payload-tracker
- 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 = payload-tracker-prod
- instance = 10.131.16.96:8383
- jiralert = RHCLOUD
- job = deployment-validation-operator-metrics
- kind = Deployment
- name = payload-tracker-frontend
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-6cbcbbbfd5-m4bgf
- 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.