From d52b0f58e8603832baba90fdde9d7e451a2375c2 Mon Sep 17 00:00:00 2001 From: devincd <505259926@qq.com> Date: Fri, 18 Dec 2020 15:13:46 +0800 Subject: [PATCH] Update container-lifecycle-hooks.md --- .../en/docs/concepts/containers/container-lifecycle-hooks.md | 2 +- 1 file changed, 1 insertion(+), 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 fa74d94221..b315ba6f59 100644 --- a/content/en/docs/concepts/containers/container-lifecycle-hooks.md +++ b/content/en/docs/concepts/containers/container-lifecycle-hooks.md @@ -57,7 +57,7 @@ Resources consumed by the command are counted against the Container. When a Container lifecycle management hook is called, 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. +`httpGet` and `tcpSocket` 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,