whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #23699 from Cweiping/feature/clairly_exec_action

Browse Source 
clarify the execution contexts of hook handlers with different action
This commit is contained in:
Kubernetes Prow Robot
2020-10-09 21:28:46 -07:00
committed by GitHub
parent 7a7b6789b8 10ebb11f20
commit 7617c89207
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/containers/container-lifecycle-hooks.md
+2 -1
View File
@@ -56,7 +56,8 @@ Resources consumed by the command are counted against the Container.
### Hook handler execution ### Hook handler execution
When a Container lifecycle management hook is called, 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. Hook handler calls are synchronous within the context of the Pod containing the Container.
This means that for a `PostStart` hook, This means that for a `PostStart` hook,