From 44897f6997950581e4bd7a7c05a5d2c18b58410f Mon Sep 17 00:00:00 2001 From: Christoph Maser Date: Mon, 9 Oct 2017 03:11:51 +0200 Subject: [PATCH] change update to disruptions (#5809) the context suggests it should be "which cause voluntary disruptions" instead of "which cause voluntary updates" --- docs/concepts/workloads/pods/disruptions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/workloads/pods/disruptions.md b/docs/concepts/workloads/pods/disruptions.md index 89c324b5bc..e1af0e4382 100644 --- a/docs/concepts/workloads/pods/disruptions.md +++ b/docs/concepts/workloads/pods/disruptions.md @@ -78,8 +78,8 @@ or across zones (if using a The frequency of voluntary disruptions varies. On a basic Kubernetes cluster, there are no voluntary disruptions at all. However, your cluster administrator or hosting provider -may run some additional services which cause voluntary disruptions. For example, -rolling out node software updates can cause voluntary updates. Also, some implementations +may run some additional services which cause voluntary disruptions. For example, +rolling out node software updates can cause voluntary disruptions. Also, some implementations of cluster (node) autoscaling may cause voluntary disruptions to defragment and compact nodes. You cluster administrator or hosting provider should have documented what level of voluntary disruptions, if any, to expect.