About this tag
Node Auto-Provisioning in Azure Kubernetes Service (AKS) uses Karpenter to automatically create, remove, replace, or consolidate nodes based on pending pods and cluster efficiency. Microsoft's guidance warns that workload-level Pod Disruption Budgets (PDBs) do not replace node-level budgets, as automated cost optimization can stall maintenance or disrupt applications. Administrators should understand how NAP interacts with disruption controls to avoid unintended downtime. This tag covers AKS operational topics including node scaling, cost optimization, and maintenance planning for enterprise IT teams managing Kubernetes clusters on Microsoft Azure.
  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...