From c4a79558bf031820aa437c496f094cce2815b845 Mon Sep 17 00:00:00 2001
From: howieyuen <howieyuen@outlook.com>
Date: Tue, 1 Mar 2022 17:10:59 +0800
Subject: [PATCH] [zh]resync api-eviction.md and fix glossary hyper link issue

---
 .../scheduling-eviction/api-eviction.md       | 184 +++++++++++++++++-
 .../docs/reference/glossary/api-eviction.md   |   4 +-
 2 files changed, 178 insertions(+), 10 deletions(-)

diff --git a/content/zh/docs/concepts/scheduling-eviction/api-eviction.md b/content/zh/docs/concepts/scheduling-eviction/api-eviction.md
index ee90cf9dd6..f51af2f678 100644
--- a/content/zh/docs/concepts/scheduling-eviction/api-eviction.md
+++ b/content/zh/docs/concepts/scheduling-eviction/api-eviction.md
@@ -13,14 +13,20 @@ weight: 70
 {{< glossary_definition term_id="api-eviction" length="short" >}} </br>
 
 <!-- 
-You can request eviction by directly calling the Eviction API 
-using a client of the kube-apiserver, like the `kubectl drain` command. 
-This creates an `Eviction` object, which causes the API server to terminate the Pod. 
+You can request eviction by calling the Eviction API directly, or programmatically
+using a client of the {{<glossary_tooltip term_id="kube-apiserver" text="API server">}}, like the `kubectl drain` command. This
+creates an `Eviction` object, which causes the API server to terminate the Pod.
 
 API-initiated evictions respect your configured [`PodDisruptionBudgets`](/docs/tasks/run-application/configure-pdb/)
 and [`terminationGracePeriodSeconds`](/docs/concepts/workloads/pods/pod-lifecycle#pod-termination). 
+
+Using the API to create an Eviction object for a Pod is like performing a
+policy-controlled [`DELETE` operation](/docs/reference/kubernetes-api/workload-resources/pod-v1/#delete-delete-a-pod)
+on the Pod. 
 -->
-你可以通过 kube-apiserver 的客户端，比如 `kubectl drain` 这样的命令，直接调用 Eviction API 发起驱逐。
+你可以通过直接调用 Eviction API 发起驱逐，也可以通过编程的方式使用
+{{<glossary_tooltip term_id="kube-apiserver" text="API 服务器">}}的客户端来发起驱逐，
+比如 `kubectl drain` 命令。
 此操作创建一个 `Eviction` 对象，该对象再驱动 API 服务器终止选定的 Pod。
 
 API 发起的驱逐将遵从你的
@@ -28,11 +34,173 @@ API 发起的驱逐将遵从你的
 和 [`terminationGracePeriodSeconds`](/zh/docs/concepts/workloads/pods/pod-lifecycle#pod-termination)
 配置。
 
+使用 API 创建 Eviction 对象，就像对 Pod 执行策略控制的
+[`DELETE` 操作](/zh/docs/reference/kubernetes-api/workload-resources/pod-v1/#delete-delete-a-pod)
+
+<!--
+## Calling the Eviction API
+
+You can use a [Kubernetes language client](/docs/tasks/administer-cluster/access-cluster-api/#programmatic-access-to-the-api)
+to access the Kubernetes API and create an `Eviction` object. To do this, you
+POST the attempted operation, similar to the following example:
+-->
+## 调用 Eviction API
+
+你可以使用 [Kubernetes 语言客户端](/zh/docs/tasks/administer-cluster/access-cluster-api/#programmatic-access-to-the-api)
+来访问 Kubernetes API 并创建 `Eviction` 对象。
+要执行此操作，你应该用 POST 发出要尝试的请求，类似于下面的示例：
+
+{{< tabs name="Eviction_example" >}}
+{{% tab name="policy/v1" %}}
+{{< note >}}
+<!-- `policy/v1` Eviction is available in v1.22+. Use `policy/v1beta1` with prior releases. -->
+`policy/v1`  版本的 Eviction 在 v1.22 以及更高的版本中可用，之前的发行版本使用 `policy/v1beta1` 版本。
+{{< /note >}}
+
+```json
+{
+  "apiVersion": "policy/v1",
+  "kind": "Eviction",
+  "metadata": {
+    "name": "quux",
+    "namespace": "default"
+  }
+}
+```
+{{% /tab %}}
+{{% tab name="policy/v1beta1" %}}
+{{< note >}}
+<!-- Deprecated in v1.22 in favor of `policy/v1` -->
+在 v1.22 版本废弃以支持 `policy/v1`
+{{< /note >}}
+
+```json
+{
+  "apiVersion": "policy/v1beta1",
+  "kind": "Eviction",
+  "metadata": {
+    "name": "quux",
+    "namespace": "default"
+  }
+}
+```
+{{% /tab %}}
+{{< /tabs >}}
+
+<!-- 
+Alternatively, you can attempt an eviction operation by accessing the API using
+`curl` or `wget`, similar to the following example:
+-->
+或者，你可以通过使用 `curl` 或者 `wget` 来访问 API 以尝试驱逐操作，类似于以下示例：
+
+```bash
+curl -v -H 'Content-type: application/json' https://your-cluster-api-endpoint.example/api/v1/namespaces/default/pods/quux/eviction -d @eviction.json
+```
+
+<!-- 
+## How API-initiated eviction works
+
+When you request an eviction using the API, the API server performs admission
+checks and responds in one of the following ways:
+-->
+
+## API 发起驱逐的工作原理
+
+当你使用 API 来请求驱逐时，API 服务器将执行准入检查，并通过以下方式之一做出响应：
+
+<!-- 
+* `200 OK`: the eviction is allowed, the `Eviction` subresource is created, and
+  the Pod is deleted, similar to sending a `DELETE` request to the Pod URL.
+* `429 Too Many Requests`: the eviction is not currently allowed because of the
+  configured {{<glossary_tooltip term_id="pod-disruption-budget" text="PodDisruptionBudget">}}.
+  You may be able to attempt the eviction again later. You might also see this
+  response because of API rate limiting. 
+* `500 Internal Server Error`: the eviction is not allowed because there is a
+  misconfiguration, like if multiple PodDisruptionBudgets reference the same Pod.
+-->
+* `200 OK`：允许驱逐，子资源 `Eviction` 被创建，并且 Pod 被删除，
+  类似于发送一个 `DELETE` 请求到 Pod 地址。
+* `429 Too Many Requests`：当前不允许驱逐，因为配置了 {{<glossary_tooltip term_id="pod-disruption-budget" text="PodDisruptionBudget">}}。
+  你可以稍后再尝试驱逐。你也可能因为 API 速率限制而看到这种响应。
+* `500 Internal Server Error`：不允许驱逐，因为存在配置错误，
+  例如存在多个 PodDisruptionBudgets 引用同一个 Pod。
+
+<!--
+If the Pod you want to evict isn't part of a workload that has a
+PodDisruptionBudget, the API server always returns `200 OK` and allows the
+eviction. 
+
+If the API server allows the eviction, the Pod is deleted as follows:
+-->
+如果你想驱逐的 Pod 不属于有 PodDisruptionBudget 的工作负载，
+API 服务器总是返回 `200 OK` 并且允许驱逐。
+
+如果 API 服务器允许驱逐，Pod 按照如下方式删除：
+
+<!--
+1. The `Pod` resource in the API server is updated with a deletion timestamp,
+   after which the API server considers the `Pod` resource to be terminated. The
+   `Pod` resource is also marked with the configured grace period.
+1. The {{<glossary_tooltip term_id="kubelet" text="kubelet">}} on the node where the local Pod is running notices that the `Pod`
+   resource is marked for termination and starts to gracefully shut down the
+   local Pod.
+1. While the kubelet is shutting the Pod down, the control plane removes the Pod
+   from {{<glossary_tooltip term_id="endpoint" text="Endpoint">}} and
+   {{<glossary_tooltip term_id="endpoint-slice" text="EndpointSlice">}}
+   objects. As a result, controllers no longer consider the Pod as a valid object.
+1. After the grace period for the Pod expires, the kubelet forcefully terminates
+   the local Pod.
+1. The kubelet tells the API server to remove the `Pod` resource.
+1. The API server deletes the `Pod` resource.
+-->
+1. API 服务器中的 `Pod` 资源会更新上删除时间戳，之后 API 服务器会认为此 `Pod` 资源将被终止。
+   此 `Pod` 资源还会标记上配置的宽限期。
+1. 本地运行状态的 Pod 所处的节点上的 {{<glossary_tooltip term_id="kubelet" text="kubelet">}}
+   注意到 `Pod` 资源被标记为终止，并开始优雅停止本地 Pod。
+1. 当 kubelet 停止 Pod 时，控制面从 {{<glossary_tooltip term_id="endpoint" text="Endpoint">}}
+   和 {{<glossary_tooltip term_id="endpoint-slice" text="EndpointSlice">}} 
+   对象中移除该 Pod。因此，控制器不再将此 Pod 视为有用对象。
+1. Pod 的宽限期到期后，kubelet 强制终止本地 Pod。
+1. kubelet 告诉 API 服务器删除 `Pod` 资源。
+1. API 服务器删除 `Pod` 资源。
+
+<!-- 
+## Troubleshooting stuck evictions
+
+In some cases, your applications may enter a broken state, where the Eviction
+API will only return `429` or `500` responses until you intervene. This can 
+happen if, for example, a ReplicaSet creates pods for your application but new 
+pods do not enter a `Ready` state. You may also notice this behavior in cases
+where the last evicted Pod had a long termination grace period.
+-->
+## 解决驱逐被卡住的问题
+
+在某些情况下，你的应用可能进入中断状态，
+在你干预之前，驱逐 API 总是返回 `429` 或 `500`。
+例如，如果 ReplicaSet 为你的应用程序创建了 Pod，
+但新的 Pod 没有进入 `Ready` 状态，就会发生这种情况。
+在最后一个被驱逐的 Pod 有很长的终止宽限期的情况下，你可能也会注意到这种行为。
+
+<!-- 
+If you notice stuck evictions, try one of the following solutions: 
+
+* Abort or pause the automated operation causing the issue. Investigate the stuck
+  application before you restart the operation.
+* Wait a while, then directly delete the Pod from your cluster control plane
+  instead of using the Eviction API.
+-->
+如果你注意到驱逐被卡住，请尝试以下解决方案之一：
+
+* 终止或暂停导致问题的自动化操作，重新启动操作之前，请检查被卡住的应用程序。
+* 等待一段时间后，直接从集群控制平面删除 Pod，而不是使用 Eviction API。
+
 ## {{% heading "whatsnext" %}}
 
 <!-- 
-* Learn about [Node-pressure Eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/)
-* Learn about [Pod Priority and Preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
+* Learn how to protect your applications with a [Pod Disruption Budget](/docs/tasks/run-application/configure-pdb/).
+* Learn about [Node-pressure Eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/).
+* Learn about [Pod Priority and Preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/).
 -->
-* 了解[节点压力引发的驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/)
-* 了解 [Pod 优先级和抢占](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
+* 了解如何使用 [Pod 干扰预算](/zh/docs/tasks/run-application/configure-pdb/) 保护你的应用。
+* 了解[节点压力引发的驱逐](/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/)。
+* 了解 [Pod 优先级和抢占](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)。
diff --git a/content/zh/docs/reference/glossary/api-eviction.md b/content/zh/docs/reference/glossary/api-eviction.md
index 9ce3069879..fc5c87c33f 100644
--- a/content/zh/docs/reference/glossary/api-eviction.md
+++ b/content/zh/docs/reference/glossary/api-eviction.md
@@ -28,8 +28,8 @@ API-initiated eviction is the process by which you use the [Eviction API](/docs/
 to create an `Eviction` object that triggers graceful pod termination.
 -->
 API 发起的驱逐是一个先调用
-[Eviction API](/docs/reference/generated/kubernetes-api/{{<param "version">}}/create-eviction-pod-v1-core)
-创建驱逐对象，再由该对象体面地中止 Pod 的过程。
+[Eviction API](/docs/reference/generated/kubernetes-api/{{<param "version">}}/#create-eviction-pod-v1-core)
+创建 `Eviction` 对象，再由该对象体面地中止 Pod 的过程。
 
 <!--more-->