[zh] sync /debug-cluster/_index.md

content/zh-cn/docs/tasks/debug/debug-cluster/_index.md

@@ -60,7 +60,13 @@ kubectl cluster-info dump
 <!-- 
 ### Example: debugging a down/unreachable node
 
-Sometimes when debugging it can be useful to look at the status of a node -- for example, because you've noticed strange behavior of a Pod that's running on the node, or to find out why a Pod won't schedule onto the node. As with Pods, you can use `kubectl describe node` and `kubectl get node -o yaml` to retrieve detailed information about nodes. For example, here's what you'll see if a node is down (disconnected from the network, or kubelet dies and won't restart, etc.). Notice the events that show the node is NotReady, and also notice that the pods are no longer running (they are evicted after five minutes of NotReady status).
+Sometimes when debugging it can be useful to look at the status of a node -- for example, because
+you've noticed strange behavior of a Pod that's running on the node, or to find out why a Pod
+won't schedule onto the node. As with Pods, you can use `kubectl describe node` and `kubectl get
+node -o yaml` to retrieve detailed information about nodes. For example, here's what you'll see if
+a node is down (disconnected from the network, or kubelet dies and won't restart, etc.). Notice
+the events that show the node is NotReady, and also notice that the pods are no longer running
+(they are evicted after five minutes of NotReady status).
 -->
 ### 示例：调试关闭/无法访问的节点 {#example-debugging-a-down-unreachable-node}
 
@@ -279,11 +285,10 @@ of the relevant log files.  On systemd-based systems, you may need to use `journ
 * `/var/log/kubelet.log` - logs from the kubelet, responsible for running containers on the node
 * `/var/log/kube-proxy.log` - logs from `kube-proxy`, which is responsible for directing traffic to Service endpoints
 -->
-
 ### 工作节点 {#worker-nodes}
 
-* `/var/log/kubelet.log` —— 来自 `kubelet` 的日志，负责在节点运行容器
-* `/var/log/kube-proxy.log` —— 来自 `kube-proxy` 的日志，负责将流量转发到服务端点
+* `/var/log/kubelet.log` —— 负责在节点运行容器的 `kubelet` 所产生的日志
+* `/var/log/kube-proxy.log` —— 负责将流量转发到服务端点的 `kube-proxy` 所产生的日志
 
 <!-- 
 ## Cluster failure modes
@@ -453,13 +458,15 @@ This is an incomplete list of things that could go wrong, and how to adjust your
   [monitoring resource usage](/docs/tasks/debug/debug-cluster/resource-usage-monitoring/)
 * Use Node Problem Detector to
   [monitor node health](/docs/tasks/debug/debug-cluster/monitor-node-health/)
+* Use `kubectl debug node` to [debug Kubernetes nodes](/docs/tasks/debug/debug-cluster/kubectl-node-debug) 
 * Use `crictl` to [debug Kubernetes nodes](/docs/tasks/debug/debug-cluster/crictl/)
 * Get more information about [Kubernetes auditing](/docs/tasks/debug/debug-cluster/audit/)
 * Use `telepresence` to [develop and debug services locally](/docs/tasks/debug/debug-cluster/local-debugging/)
 -->
 * 了解[资源指标管道](/zh-cn/docs/tasks/debug/debug-cluster/resource-metrics-pipeline/)中可用的指标
 * 发现用于[监控资源使用](/zh-cn/docs/tasks/debug/debug-cluster/resource-usage-monitoring/)的其他工具
 * 使用节点问题检测器[监控节点健康](/zh-cn/docs/tasks/debug/debug-cluster/monitor-node-health/)
+* 使用 `kubectl debug node` [调试 Kubernetes 节点](/zh-cn/docs/tasks/debug/debug-cluster/kubectl-node-debug)
 * 使用 `crictl` 来[调试 Kubernetes 节点](/zh-cn/docs/tasks/debug/debug-cluster/crictl/)
 * 获取更多关于 [Kubernetes 审计](/zh-cn/docs/tasks/debug/debug-cluster/audit/)的信息
 * 使用 `telepresence` [本地开发和调试服务](/zh-cn/docs/tasks/debug/debug-cluster/local-debugging/)