[zh] Fix some bad links in tasks section
This commit is contained in:
@@ -345,5 +345,5 @@ kubectl delete deployment frontend backend
|
|||||||
-->
|
-->
|
||||||
* 进一步了解 [Service](/zh/docs/concepts/services-networking/service/)
|
* 进一步了解 [Service](/zh/docs/concepts/services-networking/service/)
|
||||||
* 进一步了解 [ConfigMap](/zh/docs/tasks/configure-pod-container/configure-pod-configmap/)
|
* 进一步了解 [ConfigMap](/zh/docs/tasks/configure-pod-container/configure-pod-configmap/)
|
||||||
* 进一步了解 [Service 和 Pods 的 DNS](/docs/concepts/services-networking/dns-pod-service/)
|
* 进一步了解 [Service 和 Pods 的 DNS](/zh/docs/concepts/services-networking/dns-pod-service/)
|
||||||
|
|
||||||
|
|||||||
@@ -4,7 +4,6 @@ content_type: task
|
|||||||
min-kubernetes-server-version: 1.5
|
min-kubernetes-server-version: 1.5
|
||||||
---
|
---
|
||||||
<!--
|
<!--
|
||||||
---
|
|
||||||
reviewers:
|
reviewers:
|
||||||
- davidopp
|
- davidopp
|
||||||
- mml
|
- mml
|
||||||
@@ -13,7 +12,6 @@ reviewers:
|
|||||||
title: Safely Drain a Node
|
title: Safely Drain a Node
|
||||||
content_type: task
|
content_type: task
|
||||||
min-kubernetes-server-version: 1.5
|
min-kubernetes-server-version: 1.5
|
||||||
---
|
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<!-- overview -->
|
<!-- overview -->
|
||||||
@@ -264,7 +262,14 @@ eviction API will never return anything other than 429 or 500.
|
|||||||
For example: this can happen if ReplicaSet is creating Pods for your application but
|
For example: this can happen if ReplicaSet is creating Pods for your application but
|
||||||
the replacement Pods do not become `Ready`. You can also see similar symptoms if the
|
the replacement Pods do not become `Ready`. You can also see similar symptoms if the
|
||||||
last Pod evicted has a very long termination grace period.
|
last Pod evicted has a very long termination grace period.
|
||||||
|
-->
|
||||||
|
## 驱逐阻塞
|
||||||
|
|
||||||
|
在某些情况下,应用程序可能会到达一个中断状态,除了 429 或 500 之外,它将永远不会返回任何内容。
|
||||||
|
例如 ReplicaSet 创建的替换 Pod 没有变成就绪状态,或者被驱逐的最后一个
|
||||||
|
Pod 有很长的终止宽限期,就会发生这种情况。
|
||||||
|
|
||||||
|
<!--
|
||||||
In this case, there are two potential solutions:
|
In this case, there are two potential solutions:
|
||||||
|
|
||||||
- Abort or pause the automated operation. Investigate the reason for the stuck application,
|
- Abort or pause the automated operation. Investigate the reason for the stuck application,
|
||||||
@@ -275,12 +280,6 @@ In this case, there are two potential solutions:
|
|||||||
Kubernetes does not specify what the behavior should be in this case; it is up to the
|
Kubernetes does not specify what the behavior should be in this case; it is up to the
|
||||||
application owners and cluster owners to establish an agreement on behavior in these cases.
|
application owners and cluster owners to establish an agreement on behavior in these cases.
|
||||||
-->
|
-->
|
||||||
## 驱逐阻塞
|
|
||||||
|
|
||||||
在某些情况下,应用程序可能会到达一个中断状态,除了 429 或 500 之外,它将永远不会返回任何内容。
|
|
||||||
例如 ReplicaSet 创建的替换 Pod 没有变成就绪状态,或者被驱逐的最后一个
|
|
||||||
Pod 有很长的终止宽限期,就会发生这种情况。
|
|
||||||
|
|
||||||
在这种情况下,有两种可能的解决方案:
|
在这种情况下,有两种可能的解决方案:
|
||||||
|
|
||||||
- 中止或暂停自动操作。调查应用程序卡住的原因,并重新启动自动化。
|
- 中止或暂停自动操作。调查应用程序卡住的原因,并重新启动自动化。
|
||||||
@@ -291,12 +290,9 @@ Kubernetes 并没有具体说明在这种情况下应该采取什么行为,
|
|||||||
|
|
||||||
## {{% heading "whatsnext" %}}
|
## {{% heading "whatsnext" %}}
|
||||||
|
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
* Follow steps to protect your application by [configuring a Pod Disruption Budget](/docs/tasks/run-application/configure-pdb/).
|
* Follow steps to protect your application by [configuring a Pod Disruption Budget](/docs/tasks/run-application/configure-pdb/).
|
||||||
* Learn more about [maintenance on a node](/docs/tasks/administer-cluster/cluster-management/#maintenance-on-a-node).
|
|
||||||
-->
|
-->
|
||||||
* 执行[配置 PDB](/zh/docs/tasks/run-application/configure-pdb/)中的各个步骤,
|
* 执行[配置 PDB](/zh/docs/tasks/run-application/configure-pdb/)中的各个步骤,
|
||||||
保护你的应用
|
保护你的应用
|
||||||
* 进一步了解[节点维护](/zh/docs/tasks/administer-cluster/cluster-management/#maintenance-on-a-node)。
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user