From f88ea20e245affc878e47d96e3b4f57bea8992b4 Mon Sep 17 00:00:00 2001 From: Sophy417 <53026875+Sophy417@users.noreply.github.com> Date: Tue, 17 Mar 2020 21:42:23 +0800 Subject: [PATCH] update zh-trans content/zh/docs/reference/glossary/disruption.md (#19428) * Create disruption.md * Update disruption.md * Update disruption.md --- .../zh/docs/reference/glossary/disruption.md | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 content/zh/docs/reference/glossary/disruption.md diff --git a/content/zh/docs/reference/glossary/disruption.md b/content/zh/docs/reference/glossary/disruption.md new file mode 100644 index 0000000000..6dcd2525b3 --- /dev/null +++ b/content/zh/docs/reference/glossary/disruption.md @@ -0,0 +1,50 @@ +--- +title: 干扰 +id: disruption +date: 2019-09-10 +full_link: /docs/concepts/workloads/pods/disruptions/ +short_description: > + 导致 Pod 停止服务的事件 +aka: +tags: +- fundamental +--- + + +干扰是导致一个或多个 {{< glossary_tooltip term_id="pod" text="Pod" >}} 无法提供服务的事件。 +干扰会对依赖于被影响的 Pod 的工作负载资源(例如{{< glossary_tooltip term_id="deployment" >}})产生影响。 + + + + +如果你作为集群的运维人员销毁了属于某个应用程序的 Pod, Kubernetes 称之为 +_自愿性干扰_。 +如果由于节点故障或影响更大故障区域的故障使 Pod 离线,Kubernetes 称这是 _非自愿干扰_。 + + +请参看 [干扰](/docs/concepts/workloads/pods/disruptions/) 以获得更多信息。