From 97495989fcccf6427a2fb6939f5ed2293e941aeb Mon Sep 17 00:00:00 2001 From: wiggitywhitney Date: Sun, 21 Nov 2021 17:23:54 -0600 Subject: [PATCH] Clarify PDB line in disruptions concept page --- content/en/docs/concepts/workloads/pods/disruptions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md index 430d4b7155..055fc0a65d 100644 --- a/content/en/docs/concepts/workloads/pods/disruptions.md +++ b/content/en/docs/concepts/workloads/pods/disruptions.md @@ -128,8 +128,8 @@ The "intended" number of pods is computed from the `.spec.replicas` of the workl that is managing those pods. The control plane discovers the owning workload resource by examining the `.metadata.ownerReferences` of the Pod. -PDBs cannot prevent [involuntary disruptions](#voluntary-and-involuntary-disruptions) from -occurring, but they do count against the budget. +[Involuntary disruptions](#voluntary-and-involuntary-disruptions) cannot be prevented by PDBs; however they +do count against the budget. Pods which are deleted or unavailable due to a rolling upgrade to an application do count against the disruption budget, but workload resources (such as Deployment and StatefulSet)