From 3016f7d66bd280b7252cf536696793c50323a341 Mon Sep 17 00:00:00 2001 From: Sebastian Bernauer Date: Thu, 13 Aug 2026 14:52:28 +0200 Subject: [PATCH] Add a warning on setting PDB `maxUnavailable` to `0` --- modules/concepts/pages/operations/pod_disruptions.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/modules/concepts/pages/operations/pod_disruptions.adoc b/modules/concepts/pages/operations/pod_disruptions.adoc index ae587f02d..d24db0529 100644 --- a/modules/concepts/pages/operations/pod_disruptions.adoc +++ b/modules/concepts/pages/operations/pod_disruptions.adoc @@ -48,6 +48,12 @@ You can configure 1. Whether PDBs are written at all 2. The `maxUnavailable` replicas for this role PDB +[WARNING] +==== +Setting `maxUnavailable` to `0` means no voluntary disruptions are allowed. +This can block Kubernetes nodes from being drained, talk with your Kubernetes cluster provider first! +==== + The following example 1. Sets `maxUnavailable` for NameNodes to `1`