If the pod isn't created before the timeout is reached, this adds a
unique exit code so users can automatically retry in this case. Without
this it exits 1 which is difficult to differentiate between a real job
error in most cases. Ideally buildkite would show a timeout in this case
since this timeout is derived from that, but it's seems to race that
If the pod isn't created before the timeout is reached, this adds a unique exit code so users can automatically retry in this case. Without this it exits 1 which is difficult to differentiate between a real job error in most cases. Ideally buildkite would show a timeout in this case since this timeout is derived from that, but it's seems to race that