<p>While I understand the use of minAvailable and maxUnavailable to an extent, I wonder why are these two options exposed when one appears to be the complement of the other.</p>
<p>Given that PDBs are immutable, changes to these parameters are rarely made (by redeploying PDB).</p>
<p>Is there anything that I am missing to realize here?</p>

<p><code>minAvailable</code> and <code>maxUnavailable</code> are mutually exclusive, it's basically in the <a href="https://kubernetes.io/docs/tasks/run-application/configure-pdb/" rel="noreferrer">K8s docs</a> 📄📄:</p>
<blockquote>
<p>You can specify only one of maxUnavailable and minAvailable in a single PodDisruptionBudget. maxUnavailable can only be used to control the eviction of pods that have an associated controller managing them.</p>
</blockquote>
<p>An associated controller meaning: a deployment, statefulset, daemonset, etc.</p>
