whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Disruptions: make clearer not all voluntary disruptions are constrained by PDBs (#11619)

Browse Source 
* 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 <davidxia@users.noreply.github.com>

* Update content/en/docs/concepts/workloads/pods/disruptions.md

Co-Authored-By: davidxia <davidxia@users.noreply.github.com>

* Update disruptions.md
This commit is contained in:
David Xia
2019-02-17 10:27:11 -05:00
committed by Kubernetes Prow Robot
parent 43d42674e9
commit cb354f641d
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/pods/disruptions.md
+6 -1
View File
@@ -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. to determine if any sources of voluntary disruptions are enabled for your cluster.
If none are enabled, you can skip creating Pod Disruption Budgets. 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 ## Dealing with Disruptions
Here are some ways to mitigate involuntary 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 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) 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`). and the Kubernetes-on-GCE cluster upgrade script (`cluster/gce/upgrade.sh`).
When a cluster administrator wants to drain a node When a cluster administrator wants to drain a node