Skip to content

Commit 33b7cad

Browse files
authored
Merge pull request #33620 from kinzhi/kinzhi102
[zh]Update quote /docs/tasks/debug/debug-application/debug-running-pod
2 parents bd67bd9 + 8725354 commit 33b7cad

File tree

2 files changed

+4
-5
lines changed

2 files changed

+4
-5
lines changed

content/zh/docs/concepts/cluster-administration/manage-deployment.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -721,9 +721,8 @@ That's it! The Deployment will declaratively update the deployed nginx applicati
721721
## {{% heading "whatsnext" %}}
722722

723723
<!--
724-
- [Learn about how to use `kubectl` for application introspection and debugging.](/docs/tasks/debug-application-cluster/debug-application-introspection/)
724+
- [Learn about how to use `kubectl` for application introspection and debugging.](/docs/tasks/debug/debug-application/debug-running-pod/)
725725
- [Configuration Best Practices and Tips](/docs/concepts/configuration/overview/)
726726
-->
727-
- 学习[如何使用 `kubectl` 观察和调试应用](/zh/docs/tasks/debug-application-cluster/debug-application-introspection/)
727+
- 学习[如何使用 `kubectl` 观察和调试应用](/zh/docs/tasks/debug/debug-application/debug-running-pod/)
728728
- 阅读[配置最佳实践和技巧](/zh/docs/concepts/configuration/overview/)
729-

content/zh/docs/concepts/containers/runtime-class.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -159,13 +159,13 @@ spec:
159159
This will instruct the kubelet to use the named RuntimeClass to run this pod. If the named
160160
RuntimeClass does not exist, or the CRI cannot run the corresponding handler, the pod will enter the
161161
`Failed` terminal [phase](/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase). Look for a
162-
corresponding [event](/docs/tasks/debug-application-cluster/debug-application-introspection/) for an
162+
corresponding [event](/docs/tasks/debug/debug-application/debug-running-pod/) for an
163163
error message.
164164
-->
165165
这一设置会告诉 kubelet 使用所指的 RuntimeClass 来运行该 pod。
166166
如果所指的 RuntimeClass 不存在或者 CRI 无法运行相应的 handler,
167167
那么 pod 将会进入 `Failed` 终止[阶段](/zh/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase)。
168-
你可以查看相应的[事件](/zh/docs/tasks/debug-application-cluster/debug-application-introspection/),
168+
你可以查看相应的[事件](/zh/docs/tasks/debug/debug-application/debug-running-pod/),
169169
获取执行过程中的错误信息。
170170

171171
<!--

0 commit comments

Comments
 (0)