<p>Kubernetes' <code>.spec.revisionHistoryLimit</code> is used in keeping track of changes to the Deployment definition. Since these definitions are small yaml files, it doesn't seem like much (given the typical conditions of a modern cloud server) to keep 100's or more of these definitions around if necessary.</p>

<p>According to the <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#clean-up-policy" rel="noreferrer">documentation</a>, it is going to be set to 2 (instead of unlimited). Why is this?</p>

<p>Keeping it unlimited would eventually clog up etcd and iiuc etcd isn't designed for big data usages. Also the Kubernetes control plane is syncing and downloading regularly, which means there would be much unnecessary data to process. Just imagine a service with daily deployments, which runs for over a year.</p>
<p>And setting this to a high-ish number like 100 seems very random to me. Why not 1000 or 9001? Besides that, I cannot imagine anyone who might want to roll back something a hundred versions.</p>
<p>Anyway, we are only talking about a default setting, so you can set it to a very high number, if your use case requires it.</p>
