From 16e3ad4baeb4657bfb0f49f9be6037ecab0c98bf Mon Sep 17 00:00:00 2001 From: Charles Uneze Date: Fri, 7 Jun 2024 16:54:43 +0100 Subject: [PATCH] Update container-lifecycle-hooks.md Co-authored-by: Ricardo Amaro Co-authored-by: Ritika <52399571+Ritikaa96@users.noreply.github.com> --- .../concepts/containers/container-lifecycle-hooks.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/content/en/docs/concepts/containers/container-lifecycle-hooks.md b/content/en/docs/concepts/containers/container-lifecycle-hooks.md index 21d6acc1d6..9b6b37263c 100644 --- a/content/en/docs/concepts/containers/container-lifecycle-hooks.md +++ b/content/en/docs/concepts/containers/container-lifecycle-hooks.md @@ -64,11 +64,10 @@ 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. -Hook handler calls are synchronous within the context of the Pod containing the Container. -This means that for a `PostStart` hook, -the Container ENTRYPOINT and hook fire asynchronously. -However, if the hook takes too long to run or hangs, -the Container cannot reach a `running` state. +The `PostStart` hook handler call is initiated when a container is created, +meaning the container ENTRYPOINT and the `PostStart` hook are triggered simultaneously. +However, if the `PostStart` hook takes too long to execute or if it hangs, +it can prevent the container from transitioning to a `running` state. `PreStop` hooks are not executed asynchronously from the signal to stop the Container; the hook must complete its execution before the TERM signal can be sent. If a `PreStop` hook hangs during