From a76055d0c198ea6abc2c68fc60de183ce3ff1d9e Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Mon, 30 Sep 2019 22:49:32 +0100 Subject: [PATCH] Add glossary entry for disruption (#16292) --- .../en/docs/reference/glossary/disruption.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 content/en/docs/reference/glossary/disruption.md diff --git a/content/en/docs/reference/glossary/disruption.md b/content/en/docs/reference/glossary/disruption.md new file mode 100644 index 0000000000..3fbf408abe --- /dev/null +++ b/content/en/docs/reference/glossary/disruption.md @@ -0,0 +1,25 @@ +--- +title: Disruption +id: disruption +date: 2019-09-10 +full_link: /docs/concepts/workloads/pods/disruptions/ +short_description: > + An event that leads to Pod(s) going out of service +aka: +tags: +- fundamental +--- + Disruptions are events that lead to one or more +{{< glossary_tooltip term_id="pod" text="Pods" >}} going out of service. +A disruption has consequences for workload resources, such as +{{< glossary_tooltip term_id="deployment" >}}, that rely on the affected +Pods. + + + +If you, as cluster operator, destroy a Pod that belongs to an application, +Kubernetes terms that a _voluntary disruption_. If a Pod goes offline +because of a Node failure, or an outage affecting a wider failure zone, +Kubernetes terms that an _involuntary disruption_. + +See [Disruptions](/docs/concepts/workloads/pods/disruptions/) for more information.