To try and figure this out I would run the command: kubectl get pods – Add the namespace param if required. Then copy the pod name and run: kubectl describe pod {POD_NAME} That should give you some information as to why it’s stuck in the initializing state.
After investigating the code base of the Kubernetes repo, so this is how the CronJob controller works: The CronJob controller will check the every 10 seconds the list of cronjobs in the given Kubernetes Client. For every CronJob, it checks how many schedules it missed in the duration from the lastScheduleTime till now. If there … Read more
As far as I’m aware there is no “official” way to do this the way you want, and that is I believe by design. Pods are supposed to be ephemeral and horizontally scalable, and Jobs are designed to exit. Having a cron job “attach” to an existing pod doesn’t fit that module. The Scheduler would … Read more
You can now set history limits, or disable history altogether, so that failed or successful CronJobs are not kept around indefinitely. See my answer here. Documentation is here. To set the history limits: The .spec.successfulJobsHistoryLimit and .spec.failedJobsHistoryLimit fields are optional. These fields specify how many completed and failed jobs should be kept. By default, they … Read more