title: Kubernetes CronJob Stops Scheduling Jobs
body: <p>Not sure what I am doing wrong, but I am experiencing an issue where CronJobs stop scheduling new Jobs. It <em>seems</em> like this happens only after a couple of failures to launch a new Job. In my specific case, Jobs were not able to start due an inability to pull the container image.</p>
  
  <p>I'm not really finding any settings that would lead to this, but I'm no expert on Kubernetes CronJobs. Configuration below:</p>
  
  <pre><code>apiVersion: batch/v1beta1
  kind: CronJob
  metadata:
    labels:
      app.kubernetes.io/instance: cron-deal-report
      app.kubernetes.io/managed-by: Tiller
      app.kubernetes.io/name: cron
      helm.sh/chart: cron-0.1.0
    name: cron-deal-report
  spec:
    concurrencyPolicy: Forbid
    failedJobsHistoryLimit: 1
    jobTemplate:
      metadata:
        creationTimestamp: null
      spec:
        template:
          spec:
            containers:
            - args:
              - -c
              - npm run script
              command:
              - /bin/sh
              env:
              image: &lt;redacted&gt;
              imagePullPolicy: Always
              name: cron
              resources: {}
              securityContext:
                runAsUser: 1000
              terminationMessagePath: /dev/termination-log
              terminationMessagePolicy: File
            dnsPolicy: ClusterFirst
            restartPolicy: Never
            schedulerName: default-scheduler
            securityContext: {}
            terminationGracePeriodSeconds: 30
    schedule: 0/15 * * * *
    successfulJobsHistoryLimit: 3
    suspend: false
  status: {}
  </code></pre>