title: Understanding backoffLimit in Kubernetes Job
body: <p>I’ve created a <code>Cronjob</code> in kubernetes with schedule(<code>8 * * * *</code>), with job’s <code>backoffLimit</code> defaulting to 6 and pod’s <code>RestartPolicy</code> to <code>Never</code>, the pods are deliberately configured to FAIL. As I understand, (for podSpec with <code>restartPolicy : Never</code>) Job controller will try to create <code>backoffLimit</code> number of pods and then it marks the job as <code>Failed</code>, so, I expected that there would be 6 pods in <code>Error</code> state.</p>
  
  <p>This is the actual Job’s status:</p>
  
  <pre><code>status:
    conditions:
    - lastProbeTime: 2019-02-20T05:11:58Z
      lastTransitionTime: 2019-02-20T05:11:58Z
      message: Job has reached the specified backoff limit
      reason: BackoffLimitExceeded
      status: "True"
      type: Failed
    failed: 5
  </code></pre>
  
  <p>Why were there only 5 failed pods instead of 6? Or is my understanding about <code>backoffLimit</code> in-correct?</p>