-
Notifications
You must be signed in to change notification settings - Fork 14.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add glossary entry for disruption (#16292)
- Loading branch information
1 parent
c774c23
commit a76055d
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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. | ||
|
||
<!--more--> | ||
|
||
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. |