[zh-cn] sync system-metrics.md system-metrics.md system-metrics.md

Author: Eason1118

content/zh-cn/docs/concepts/cluster-administration/system-metrics.md

@@ -291,19 +291,24 @@ Once a pod reaches completion (has a `restartPolicy` of `Never` or `OnFailure` a
 the series is no longer reported since the scheduler is now free to schedule other pods to run.
 The two metrics are called `kube_pod_resource_request` and `kube_pod_resource_limit`.
 
-The metrics are exposed at the HTTP endpoint `/metrics/resources` and require the same
-authorization as the `/metrics` endpoint on the scheduler. You must use the
-`--show-hidden-metrics-for-version=1.20` flag to expose these alpha stability metrics.
+The metrics are exposed at the HTTP endpoint `/metrics/resources`. They require
+authorization for the `/metrics/resources` endpoint, usually granted by a
+ClusterRole with the `get` verb for the `/metrics/resources` non-resource URL.
+
+On Kubernetes 1.21 you must use the `--show-hidden-metrics-for-version=1.20`
+flag to expose these alpha stability metrics.
 -->
 一旦 Pod 进入完成状态（其 `restartPolicy` 为 `Never` 或 `OnFailure`，且
 其处于 `Succeeded` 或 `Failed` Pod 阶段，或者已经被删除且所有容器都具有
 终止状态），该时间序列停止报告，因为调度器现在可以调度其它 Pod 来执行。
 这两个指标称作 `kube_pod_resource_request` 和 `kube_pod_resource_limit`。
 
-指标暴露在 HTTP 端点 `/metrics/resources`，与调度器上的 `/metrics` 端点
-一样要求相同的访问授权。你必须使用
-`--show-hidden-metrics-for-version=1.20` 标志才能暴露那些稳定性为 Alpha
-的指标。
+这些指标通过 HTTP 端点 `/metrics/resources` 公开出来。
+访问 `/metrics/resources` 端点需要鉴权，通常通过对
+`/metrics/resources` 非资源 URL 的 `get` 访问授予访问权限。  
+
+在 Kubernetes 1.21 中，你必须使用 `--show-hidden-metrics-for-version=1.20`
+标志来公开 Alpha 级稳定性的指标。
 
 <!--
 ## Disabling metrics

content/zh-cn/docs/concepts/containers/container-lifecycle-hooks.md

@@ -121,12 +121,14 @@ Enable the `PodLifecycleSleepActionAllowZero` feature gate if you want to set a
 
 When a Container lifecycle management hook is called,
 the Kubernetes management system executes the handler according to the hook action,
-`httpGet` , `tcpSocket` and `sleep` are executed by the kubelet process, and `exec` is executed in the container.
+`httpGet`, `tcpSocket` ([deprecated](/docs/reference/generated/kubernetes-api/v1.31/#lifecyclehandler-v1-core))
+and `sleep` are executed by the kubelet process, and `exec` is executed in the container.
 -->
 ### 回调处理程序执行   {#hook-handler-execution}
 
 当调用容器生命周期管理回调时，Kubernetes 管理系统根据回调动作执行其处理程序，
-`httpGet`、`tcpSocket` 和 `sleep` 由 kubelet 进程执行，而 `exec` 在容器中执行。
+`httpGet`、`tcpSocket`（[已弃用](/docs/reference/generated/kubernetes-api/v1.31/#lifecyclehandler-v1-core)）
+和 `sleep` 由 kubelet 进程执行，而 `exec` 在容器内执行。
 
 <!--
 The `PostStart` hook handler call is initiated when a container is created,

content/zh-cn/docs/concepts/security/_index.md

@@ -147,6 +147,7 @@ Huawei Cloud | https://www.huaweicloud.com/intl/en-us/securecenter/overallsafety
 IBM Cloud | https://www.ibm.com/cloud/security |
 Microsoft Azure | https://docs.microsoft.com/en-us/azure/security/azure-security |
 Oracle Cloud Infrastructure | https://www.oracle.com/security |
+Tencent Cloud | https://www.tencentcloud.com/solutions/data-security-and-information-protection |
 VMware vSphere | https://www.vmware.com/security/hardening-guides |
 
 {{< /table >}}
@@ -162,6 +163,7 @@ IaaS 提供商        | 链接 |
 IBM 云 | https://www.ibm.com/cloud/security |
 微软 Azure | https://docs.microsoft.com/en-us/azure/security/azure-security |
 Oracle 云基础设施| https://www.oracle.com/security |
+腾讯云 | https://www.tencentcloud.com/solutions/data-security-and-information-protection |
 VMware vSphere | https://www.vmware.com/security/hardening-guides |
 
 {{< /table >}}