Q: A CronJob job ran but the pod isn't showing in `kubectl get jobs`.
successfulJobsHistoryLimit may be 0 or 1 and old jobs were cleaned. Adjust to keep history.
#Kubernetes #Advanced Scenarios #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
successfulJobsHistoryLimit may be 0 or 1 and old jobs were cleaned. Adjust to keep history.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: successfulJobsHistoryLimit may be 0 or 1 and old jobs were cleaned. Adjust to keep history.."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: successfulJobsHistoryLimit may be 0 or 1 and old jobs were cleaned. Adjust to keep history.
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement