[zh-cn]sync endpoint-slice endpoint node-metrics

Signed-off-by: xin.li <[email protected]>

Author: my-git9

content/zh-cn/docs/reference/glossary/endpoint-slice.md

@@ -4,7 +4,7 @@ id: endpoint-slice
 date: 2018-04-12
 full_link: /zh-cn/docs/concepts/services-networking/endpoint-slices/
 short_description: >
-  一种将网络端点与 Kubernetes 资源组合在一起的方法。
+  EndpointSlices 跟踪具有匹配 Service 选择算符的 Pod 的 IP 地址。
 
 aka:
 tags:
@@ -16,25 +16,23 @@ id: endpoint-slice
 date: 2018-04-12
 full_link: /docs/concepts/services-networking/endpoint-slices/
 short_description: >
-  A way to group network endpoints together with Kubernetes resources.
+  EndpointSlices track the IP addresses of Pods with matching Service selectors.
 
 aka:
 tags:
 - networking
 -->
 
 <!--
- A way to group network endpoints together with Kubernetes resources.
+ EndpointSlices track the IP addresses of Pods with matching  {{< glossary_tooltip text="selectors" term_id="selector" >}}.
 -->
-一种将网络端点与 Kubernetes 资源组合在一起的方法。
+EndpointSlices 跟踪具有匹配{{< glossary_tooltip text="选择算符" term_id="selector" >}}的
+Pod 的 IP 地址。
 
 <!--more-->
 
 <!--
-A scalable and extensible way to group network endpoints together. These can be
-used by {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} to
-establish network routes on each {{< glossary_tooltip text="node" term_id="node" >}}.
+EndpointSlices can be configured manually for {{< glossary_tooltip text="Services" term_id="service" >}} without selectors specified.
 -->
-一种将网络端点组合在一起的可扩缩、可扩展方式。
-它们将被 {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} 用于在
-每个 {{< glossary_tooltip text="节点" term_id="node">}} 上建立网络路由。
+EndpointSlices 可以手动配置给没有指定选择算符的
+{{< glossary_tooltip text="Service" term_id="service" >}}。

content/zh-cn/docs/reference/glossary/endpoint.md

@@ -4,7 +4,7 @@ id: endpoints
 date: 2020-04-23
 full_link: 
 short_description: >
-  端点负责记录与服务（Service）的选择器相匹配的 Pod 的 IP 地址。
+  Service 的一个端点是实现该服务的 Pod 之一（或外部服务器）。
 
 aka:
 tags:
@@ -16,26 +16,35 @@ id: endpoints
 date: 2020-04-23
 full_link: 
 short_description: >
-  Endpoints track the IP addresses of Pods with matching Service selectors.
+  An endpoint of a Service is one of the Pods (or external servers) that implements the Service.
 
 aka:
 tags:
 - networking
 -->
 
 <!--
- Endpoints track the IP addresses of Pods with matching  {{< glossary_tooltip text="selectors" term_id="selector" >}}.
+ An endpoint of a {{< glossary_tooltip text="Service" term_id="service" >}} is one of the {{< glossary_tooltip text="Pods" term_id="pod" >}} (or external servers) that implements the Service.
 -->
-端点负责记录与服务的{{< glossary_tooltip text="选择器" term_id="selector" >}}相匹配的 Pod 的 IP 地址。
+一个 {{< glossary_tooltip text="Service" term_id="service" >}}
+的端点是实现该 Service 的 {{< glossary_tooltip text="Pod 之一" term_id="pod" >}}
+（或外部服务器）。
 
 <!--more-->
 
 <!--
-Endpoints can be configured manually for {{< glossary_tooltip text="Services" term_id="service" >}} without selectors specified.
+For Services with {{< glossary_tooltip text="selectors" term_id="selector" >}},
+the EndpointSlice controller will automatically create one or more {{<
+glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}} giving the
+IP addresses of the selected endpoint Pods.
 -->
-端点可以手动配置到{{< glossary_tooltip text="服务（Service）" term_id="service" >}}上，而不必指定选择器标识。
+对于带有{{< glossary_tooltip text="选择器" term_id="selector" >}}的 Service，
+EndpointSlice 控制器将自动创建一个或多个
+{{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}}，
+提供选定端点 Pod 的 IP 地址。
 
 <!--
-The {{< glossary_tooltip text="EndpointSlice" term_id="endpoint-slice" >}} resource provides a scalable and extensible alternative to Endpoints.
+EndpointSlices can also be created manually to indicate the endpoints of
+Services that have no selector specified.
 -->
-{{< glossary_tooltip text="EndpointSlice" term_id="endpoint-slice" >}} 提供了一种可伸缩、可扩展的替代方案。
+EndpointSlices 也可以手动创建，以指示没有指定选择器的服务的端点。

content/zh-cn/docs/reference/instrumentation/node-metrics.md

@@ -18,11 +18,11 @@ description: >-
 The [kubelet](/docs/reference/command-line-tools-reference/kubelet/)
 gathers metric statistics at the node, volume, pod and container level,
 and emits this information in the
-[Summary API](https://github.com/kubernetes/kubernetes/blob/7d309e0104fedb57280b261e5677d919cb2a0e2d/staging/src/k8s.io/kubelet/pkg/apis/stats/v1alpha1/types.go).
+[Summary API](/docs/reference/config-api/kubelet-stats.v1alpha1/).
 -->
 [kubelet](/zh-cn/docs/reference/command-line-tools-reference/kubelet/)
-在节点、卷、Pod 和容器级别收集统计信息，并在
-[概要 API](https://github.com/kubernetes/kubernetes/blob/7d309e0104fedb57280b261e5677d919cb2a0e2d/staging/src/k8s.io/kubelet/pkg/apis/stats/v1alpha1/types.go)
+在节点、卷、Pod 和容器级别收集统计信息，
+并在[概要 API](zh-cn/docs/reference/config-api/kubelet-stats.v1alpha1/)
 中输出这些信息。
 
 <!--
@@ -42,8 +42,11 @@ kubectl get --raw "/api/v1/nodes/minikube/proxy/stats/summary"
 <!--
 Here is the same API call using `curl`:
 
+```shell
 # You need to run "kubectl proxy" first
 # Change 8080 to the port that "kubectl proxy" assigns
+curl http://localhost:8080/api/v1/nodes/minikube/proxy/stats/summary
+```
 -->
 下面是使用 `curl` 所执行的相同 API 调用：
 
@@ -58,8 +61,8 @@ curl http://localhost:8080/api/v1/nodes/minikube/proxy/stats/summary
 Beginning with `metrics-server` 0.6.x, `metrics-server` queries the `/metrics/resource`
 kubelet endpoint, and not `/stats/summary`.
 -->
-从 `metrics-server` 0.6.x 开始，`metrics-server` 查询 `/metrics/resource` kubelet 端点，
-不查询 `/stats/summary`。
+从 `metrics-server` 0.6.x 开始，`metrics-server` 查询 `/metrics/resource`
+kubelet 端点，不查询 `/stats/summary`。
 {{< /note >}}
 
 <!--
@@ -81,6 +84,46 @@ the kubelet [fetches Pod- and container-level metric data using CRI](/docs/refer
 则 kubelet [将使用 CRI 来获取 Pod 和容器级别的指标数据](/zh-cn/docs/reference/instrumentation/cri-pod-container-metrics)，
 而不是 cAdvisor 来获取。
 
+<!--
+## Pressure Stall Information (PSI) {#psi}
+-->
+## 压力停滞信息（PSI）
+
+{{< feature-state for_k8s_version="v1.33" state="alpha" >}}
+
+<!--
+As an alpha feature, Kubernetes lets you configure kubelet to collect Linux kernel
+[Pressure Stall Information](https://docs.kernel.org/accounting/psi.html)
+(PSI) for CPU, memory and IO usage. The information is collected at node, pod and container level.
+See [Summary API](/docs/reference/config-api/kubelet-stats.v1alpha1/) for detailed schema.
+You must enable the `KubeletPSI` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+to use this feature. The information is also exposed in
+[Prometheus metrics](/docs/concepts/cluster-administration/system-metrics#psi-metrics).
+-->
+作为 Alpha 级别特性，Kubernetes 允许你配置 kubelet 来收集 Linux
+内核的[压力停滞信息](https://docs.kernel.org/accounting/psi.html)（PSI）
+的 CPU、内存和 IO 使用情况。这些信息是在节点、Pod 和容器级别上收集的。
+详细模式请参见 [Summary API](/zh-cn/docs/reference/config-api/kubelet-stats.v1alpha1/)。
+你必须启用 `KubeletPSI`
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)才能使用此特性。
+这些信息也在
+[Prometheus 指标](/zh-cn/docs/concepts/cluster-administration/system-metrics#psi-metrics)中暴露。
+
+<!--
+### Requirements
+
+Pressure Stall Information requires:
+
+- [Linux kernel versions 4.20 or later](/docs/reference/node/kernel-version-requirements#requirements-psi).
+- [cgroup v2](/docs/concepts/architecture/cgroups)
+-->
+### 要求
+
+压力停滞信息要求：
+
+- [Linux 内核版本 4.20 或更新](/zh-cn/docs/reference/node/kernel-version-requirements#requirements-psi)。
+- [CGroup v2](/zh-cn/docs/concepts/architecture/cgroups)
+
 ## {{% heading "whatsnext" %}}
 
 <!--

content/zh-cn/docs/reference/kubectl/conventions.md

@@ -46,18 +46,20 @@ For a stable output in a script:
 ## 子资源    {#subresources}
 
 <!--
-* You can use the `--subresource` beta flag for kubectl commands like `get`, `patch`,
-`edit` and `replace` to fetch and update subresources for all resources that
-support them. Currently, only the `status` and `scale` subresources are supported.
+* You can use the `--subresource` argument for kubectl subcommands such as `get`, `patch`,
+`edit`, `apply` and `replace` to fetch and update subresources for all resources that
+support them. In Kubernetes version {{< skew currentVersion >}}, only the `status`, `scale`
+and `resize` subresources are supported.
   * For `kubectl edit`, the `scale` subresource is not supported. If you use  `--subresource` with
     `kubectl edit` and specify `scale` as the subresource, the command will error out.
 * The API contract against a subresource is identical to a full resource. While updating the
 `status` subresource to a new value, keep in mind that the subresource could be potentially
 reconciled by a controller to a different value.
 -->
 
-* 你可以将 `--subresource` Beta 标志用于 kubectl 命令，例如 `get`、`patch`、`edit` 和 `replace`
-  来获取和更新所有支持子资源的资源的子资源。目前，仅支持 `status` 和 `scale` 子资源。
+* 你可以将 `--subresource` 参数用于 kubectl 命令，例如 `get`、`patch`、`edit`、`apply` 和 `replace`
+  来获取和更新所有支持子资源的资源的子资源。Kubernetes {{< skew currentVersion >}} 版本中，
+  仅支持 `status`, `scale` 和 `resize` 子资源。
   * 对于 `kubectl edit`，不支持 `scale` 子资源。如果将 `--subresource` 与 `kubectl edit` 一起使用，
     并指定 `scale` 作为子资源，则命令将会报错。
 * 针对子资源的 API 协定与完整资源相同。在更新 `status` 子资源为一个新值时，请记住，