<p>I have a pod with some terrible, buggy software in it. One reason Kubernetes is great is that it'll just restart the software when it crashes, which is awesome.</p>

<p>Kubernetes was designed for good software, not terrible software, so it does an exponential backoff while restarting pods. This means I have to wait five minutes between crashes before my pods are restarted.</p>

<p>Is there any way to cap the kubernetes backoff strategy? I'd like to change it to not wait longer than thirty seconds before starting up the pod again.</p>

<p>Unfortunately, the max back off time for container restarts is not tunable for the node reliability (i.e., too many container restarts can overwhelm the node). If you absolutely want to change it in your cluster, you will need to <a href="https://github.com/kubernetes/kubernetes/blob/a6718f59691d7b3989c4222fb21e8daeb2ff84cc/pkg/kubelet/kubelet.go#L108" rel="noreferrer">modify the max backoff time in the code</a>, compile your own kubelet binary, and distribute it onto your nodes. </p>
