title: Kubernetes pod marked as `Completed` despite the exit code `255`
body: <p><strong>Situation:</strong>
  I've got a CronJob that often fails (this is expected at the moment). Due to the fact that the container performing the job, has a side-car, the dependencies are between the containers are expressed through bash scripts and common mounts of <code>emptyDir</code> in <code>/etc/liveness</code> folder:</p>
  <pre><code>        spec:
            containers:
            - args:
              - -c
              - set -x;
                ...
                ./process; # execute the main process
                rc=$?;
                rm /etc/liveness; # clean-up
                exit $rc;
              command:
              - /bin/bash
  </code></pre>
  <p><strong>Problem:</strong>
  In the scenarios, where the job fails, I see the following in the logs:</p>
  <pre><code>+ rc=255
  + rm /etc/liveness
  + exit 255
  </code></pre>
  <p>With <code>retryPolicy</code> set to <code>never</code>, the failed pod enters the <code>Completed</code> status, which is misleading:</p>
  <pre><code>scheduler-1594015200-wl9xc   0/2     Completed     0          24m
  </code></pre>