clarify the execution contexts of hook handlers with different action types are different

Signed-off-by: Weiping Cai <weiping.cai@daocloud.io>
pull/23699/head
Weiping Cai 2020-09-05 19:58:10 +08:00
parent 377ca1f44f
commit 10ebb11f20
No known key found for this signature in database
GPG Key ID: 97CBE6D7C8EBC386
1 changed files with 2 additions and 1 deletions

View File

@ -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,