Skip to content

Commit cbf6118

Browse files
authored
Add a warning on setting PDB maxUnavailable to 0 (#922)
1 parent 0e569b8 commit cbf6118

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

modules/concepts/pages/operations/pod_disruptions.adoc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,12 @@ You can configure
4848
1. Whether PDBs are written at all
4949
2. The `maxUnavailable` replicas for this role PDB
5050

51+
[WARNING]
52+
====
53+
Setting `maxUnavailable` to `0` means no voluntary disruptions are allowed.
54+
This can block Kubernetes nodes from being drained, talk with your Kubernetes cluster provider first!
55+
====
56+
5157
The following example
5258

5359
1. Sets `maxUnavailable` for NameNodes to `1`

0 commit comments

Comments
 (0)