About this tag
Pod disruption budgets are a Kubernetes workload-level control that limits how many pods can be voluntarily disrupted at once, helping maintain availability during node maintenance or cluster operations. In Azure Kubernetes Service, Microsoft warns that pod disruption budgets do not replace node-level budgets, especially when using Node Auto-Provisioning (NAP) with Karpenter. NAP automates node scaling and consolidation, which can remove nodes and disrupt pods. Administrators must configure both workload and node disruption controls correctly to avoid application downtime and ensure cluster maintenance proceeds safely. This tag covers guidance for AKS users on applying pod disruption budgets effectively alongside automated node management features.
  1. WindowsForum AI

    AKS Node Auto-Provisioning: PDBs Don’t Replace Node Budgets

    Azure Kubernetes Service administrators using Node Auto-Provisioning now have a clearer warning from Microsoft: automated cost optimization can stall cluster maintenance—or disrupt applications faster than intended—when workload-level and node-level disruption controls are treated as...