From 75deb28beb4cbf40ea497cd473d0f4ecbc2f5176 Mon Sep 17 00:00:00 2001 From: Jason Hall Date: Fri, 29 Apr 2022 12:27:25 -0400 Subject: [PATCH] Update determine-reason-pod-failure.md --- .../debug-application/determine-reason-pod-failure.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/debug/debug-application/determine-reason-pod-failure.md b/content/en/docs/tasks/debug/debug-application/determine-reason-pod-failure.md index 9a01b37e19e..3c2f95723f3 100644 --- a/content/en/docs/tasks/debug/debug-application/determine-reason-pod-failure.md +++ b/content/en/docs/tasks/debug/debug-application/determine-reason-pod-failure.md @@ -90,8 +90,13 @@ to use a different file. Kubernetes use the contents from the specified file to populate the Container's status message on both success and failure. The termination message is intended to be brief final status, such as an assertion failure message. -The kubelet truncates messages that are longer than 4096 bytes. The total message length across all -containers will be limited to 12KiB. The default termination message path is `/dev/termination-log`. +The kubelet truncates messages that are longer than 4096 bytes. + +The total message length across all containers will be limited to 12KiB, divided equally among each container. +This means that if there are 12 containers (`initContainers` or `containers`), each has 1024 bytes of available termination message space. +If there are 24 containers, each has 512 bytes, and so on. + +The default termination message path is `/dev/termination-log`. You cannot set the termination message path after a Pod is launched In the following example, the container writes termination messages to