From cb354f641d347e0f5ce9443e5df0f48115319e8a Mon Sep 17 00:00:00 2001 From: David Xia Date: Sun, 17 Feb 2019 10:27:11 -0500 Subject: [PATCH] Disruptions: make clearer not all voluntary disruptions are constrained by PDBs (#11619) * Disruptions: make clearer not all voluntary disruptions are constrained by PDBs Currently, there's confusion on whether all voluntary disruptions are constrained by PDBs. For example, see the three comments [here](https://github.com/kubernetes/kubernetes/issues/39824#issuecomment-436322189). * Update content/en/docs/concepts/workloads/pods/disruptions.md Co-Authored-By: davidxia * Update content/en/docs/concepts/workloads/pods/disruptions.md Co-Authored-By: davidxia * Update disruptions.md --- content/en/docs/concepts/workloads/pods/disruptions.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md index 3a3ecb36cf..6725c887f4 100644 --- a/content/en/docs/concepts/workloads/pods/disruptions.md +++ b/content/en/docs/concepts/workloads/pods/disruptions.md @@ -63,6 +63,11 @@ Ask your cluster administrator or consult your cloud provider or distribution do to determine if any sources of voluntary disruptions are enabled for your cluster. If none are enabled, you can skip creating Pod Disruption Budgets. +{{< caution >}} +Not all voluntary disruptions are constrained by Pod Disruption Budgets. For example, +deleting deployments or pods bypasses Pod Disruption Budgets. +{{< /caution >}} + ## Dealing with Disruptions Here are some ways to mitigate involuntary disruptions: @@ -102,7 +107,7 @@ percentage of the total. Cluster managers and hosting providers should use tools which respect Pod Disruption Budgets by calling the [Eviction API](/docs/tasks/administer-cluster/safely-drain-node/#the-eviction-api) -instead of directly deleting pods. Examples are the `kubectl drain` command +instead of directly deleting pods or deployments. Examples are the `kubectl drain` command and the Kubernetes-on-GCE cluster upgrade script (`cluster/gce/upgrade.sh`). When a cluster administrator wants to drain a node