You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/containers/container-lifecycle-hooks.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,22 +105,22 @@ The logs for a Hook handler are not exposed in Pod events.
105
105
If a handler fails for some reason, it broadcasts an event.
106
106
For `PostStart`, this is the `FailedPostStartHook` event,
107
107
and for `PreStop`, this is the `FailedPreStopHook` event.
108
-
You can see these events by running `kubectl describe pod <pod_name>`.
109
-
Here is some example output of events from running this command:
108
+
To generate a failed `FailedPreStopHook` event yourself, modify the [lifecycle-events.yaml](https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/pods/lifecycle-events.yaml) file to change the postStart command to "badcommand" and apply it.
109
+
Here is some example output of the resulting events you see from running `kubectl describe pod lifecycle-demo`:
110
110
111
111
```
112
112
Events:
113
-
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
1m1m1 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} spec.containers{main} NormalCreated Created container with docker id 5c6a256a2567; Security:[seccomp=unconfined]
0 commit comments