This alert is triggered whenever a Jenkins job executes to:
1. Create a Kubernetes Job from a CronJob manifest 2. Trigger the backup pipeline for a specific tool
Alerts:
This runbook applies to all tools using Jenkins to trigger Kubernetes Jobs or backup pipelines.
* Success → Backup Job or pipeline has been successfully triggered. The actual backup may run later via the Job. * Failure → Backup Job was not created; backup may not occur, potentially affecting RPO.
1. Check Jenkins build status and logs:
# From Jenkins UI or CLI BUILD_NUMBER=<build_number> Jenkins → Job → Build #${BUILD_NUMBER} → Console Output
2. Check Kubernetes Job creation:
kubectl get jobs -n <NAMESPACE> kubectl describe job <JOB_NAME> -n <NAMESPACE>
3. Check if the Job has started successfully:
kubectl logs job/<JOB_NAME> -n <NAMESPACE>
4. Check Alertmanager alert (optional):
curl -s http://<alertmanager-endpoint>/api/v2/alerts | jq '.[] | select(.labels.build=="<BUILD_NUMBER>")'
* Jenkins agent cannot start or run kubectl commands * Kubernetes secret (kubeconfig) missing or invalid * Incorrect namespace or Job manifest YAML error * RBAC/permissions issues preventing Job creation * Network issues accessing Kubernetes API * Pipeline script errors
1. Verify Jenkins agent and kubeconfig secret exist and are correct 2. Validate the Kubernetes CronJob YAML:
kubectl apply -f <cronjob.yaml> --dry-run=client
3. Retry Jenkins build manually if needed 4. Ensure the namespace exists and has correct permissions 5. Ensure Jenkins agent can communicate with the Kubernetes API
* Escalate if Job cannot be created for more than one consecutive run * Notify on-call engineer if production backup pipeline may be missed
* JenkinsBuildSuccess * JenkinsBuildFailed
* Jenkins → All Jobs Overview * Kubernetes → Jobs & CronJobs for backups * Alertmanager → Jenkins Alerts