From a1ec586976f1ca58bf140af1a016c032e9b974fe Mon Sep 17 00:00:00 2001 From: xinlingchao Date: Fri, 11 Feb 2022 10:52:22 +0800 Subject: [PATCH] minor improvement --- .../docs/concepts/containers/container-lifecycle-hooks.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/zh/docs/concepts/containers/container-lifecycle-hooks.md b/content/zh/docs/concepts/containers/container-lifecycle-hooks.md index c1aed50e1f..32d86af26a 100644 --- a/content/zh/docs/concepts/containers/container-lifecycle-hooks.md +++ b/content/zh/docs/concepts/containers/container-lifecycle-hooks.md @@ -222,8 +222,10 @@ Here is some example output of the resulting events you see from running `kubect 回调处理程序的日志不会在 Pod 事件中公开。 如果处理程序由于某种原因失败，它将播放一个事件。 对于 `PostStart`，这是 `FailedPostStartHook` 事件，对于 `PreStop`，这是 `FailedPreStopHook` 事件。 -要自己生成失败的 `FailedPreStopHook` 事件，请修改 [lifecycle-events.yaml](https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/pods/lifecycle-events.yaml) 文件将 postStart 命令更改为 ”badcommand“ 并应用它。 -下面是运行 `kubectl describe pod lifecycle-demo` 所产生事件的一些示例输出： +要自己生成失败的 `FailedPreStopHook` 事件，请修改 +[lifecycle-events.yaml](https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/pods/lifecycle-events.yaml) +文件将 postStart 命令更改为 ”badcommand“ 并应用它。 +以下是通过运行 `kubectl describe pod lifecycle-demo` 后你看到的一些结果事件的示例输出： ``` Events: