-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
- JIRALERT{4f4fe0e272a1f23bf0fd72e0a6f9b3032a62a6025790ae29bf5f3075c76a0f53076c7f7b2dbe29ca0737779283984e9fd6600e190e47fad0ec08e18a17942d1d}
- alertname="deployment_validation_operator_default_service_account"
- app="automation-hub"
- cluster="crcs02ue1"
- job="deployment-validation-operator-metrics"
- service="deployment-validation-operator"
-
False
-
-
False
Alert: deployment_validation_operator_default_service_account Validation error for automation-hub: 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=automation-hub-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 = automation-hub
- 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 = automation-hub-stage
- instance = 10.130.8.60:8383
- jiralert = AAH
- job = deployment-validation-operator-metrics
- kind = Job
- name = automation-hub-job-2cdc7b7-1
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-6cbcbbbfd5-pk5lk
- 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.