From 10ebb11f206beadda2f93c47e61ddd0ad09aa8c3 Mon Sep 17 00:00:00 2001 From: Weiping Cai Date: Sat, 5 Sep 2020 19:58:10 +0800 Subject: [PATCH] clarify the execution contexts of hook handlers with different action types are different Signed-off-by: Weiping Cai --- .../en/docs/concepts/containers/container-lifecycle-hooks.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/containers/container-lifecycle-hooks.md b/content/en/docs/concepts/containers/container-lifecycle-hooks.md index 09d5530a29..5b765162a8 100644 --- a/content/en/docs/concepts/containers/container-lifecycle-hooks.md +++ b/content/en/docs/concepts/containers/container-lifecycle-hooks.md @@ -56,7 +56,8 @@ Resources consumed by the command are counted against the Container. ### Hook handler execution When a Container lifecycle management hook is called, -the Kubernetes management system executes the handler in the Container registered for that hook.  +the Kubernetes management system execute the handler according to the hook action, +`exec` and `tcpSocket` are executed in the container, and `httpGet` is executed by the kubelet process. Hook handler calls are synchronous within the context of the Pod containing the Container. This means that for a `PostStart` hook,