The CronJob Stayed Green. It Hadn't Run in 24 Days. 4 Traps Behind K3s's Silent Scheduling Failures
K3s and Kubernetes CronJobs can keep showing 'Succeeded' while quietly not running for weeks. Here's how concurrencyPolicy, startingDeadlineSeconds, the 100-missed-schedule limit, and exit code 0 combine to create silent failures, and how to monitor for it.