From f014a9789319d0d24ab1e33da0b674f13851f3ac Mon Sep 17 00:00:00 2001 From: Aliaksei Date: Sun, 20 Oct 2024 20:52:17 -0400 Subject: [PATCH] Fixed URL --- .../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 f7b7fa16a4..379487037c 100644 --- a/content/en/docs/concepts/containers/container-lifecycle-hooks.md +++ b/content/en/docs/concepts/containers/container-lifecycle-hooks.md @@ -62,7 +62,7 @@ Resources consumed by the command are counted against the Container. When a Container lifecycle management hook is called, the Kubernetes management system executes the handler according to the hook action, -`httpGet`, `tcpSocket` (deprecated[https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#lifecyclehandler-v1-core]) and `sleep` are executed by the kubelet process, and `exec` is executed in the container. +`httpGet`, `tcpSocket` ([deprecated](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#lifecyclehandler-v1-core)) and `sleep` are executed by the kubelet process, and `exec` is executed in the container. The `PostStart` hook handler call is initiated when a container is created, meaning the container ENTRYPOINT and the `PostStart` hook are triggered simultaneously.