Merge pull request #33320 from imjasonh/patch-1

Document per-container termination message limits

Author: k8s-ci-robot

content/en/docs/tasks/debug/debug-application/determine-reason-pod-failure.md

@@ -90,8 +90,12 @@ 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 is limited to 12KiB, divided equally among each container.
+For example, if there are 12 containers (`initContainers` or `containers`), each has 1024 bytes of available termination message space.
+
+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