Skip to content

Commit 211d151

Browse files
committed
minor edit to note about draining nodes
1 parent b3a9776 commit 211d151

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/resize-node-pool.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Resize node pools in Azure Kubernetes Service (AKS)
33
description: Learn how to resize node pools for a cluster in Azure Kubernetes Service (AKS) by cordoning and draining.
44
services: container-service
55
ms.topic: how-to
6-
ms.date: 02/24/2022
6+
ms.date: 02/08/2023
77
#Customer intent: As a cluster operator, I want to resize my node pools so that I can run more or larger workloads.
88
---
99

@@ -169,7 +169,7 @@ node/aks-nodepool1-31721111-vmss000002 cordoned
169169
## Drain the existing nodes
170170

171171
> [!IMPORTANT]
172-
> To successfully drain nodes and evict running pods, ensure that any PodDisruptionBudgets (PDBs) allow for at least 1 pod replica to be moved at a time, otherwise the drain/evict operation will fail. To check this, you can run `kubectl get pdb -A` and make sure `ALLOWED DISRUPTIONS` is at least 1 or higher.
172+
> To successfully drain nodes and evict running pods, ensure that any PodDisruptionBudgets (PDBs) allow for at least one pod replica to be moved at a time. Otherwise, the drain/evict operation will fail. To check this, you can run `kubectl get pdb -A` and verify `ALLOWED DISRUPTIONS` is at least one or higher.
173173
174174
Draining nodes will cause pods running on them to be evicted and recreated on the other, schedulable nodes.
175175

0 commit comments

Comments
 (0)