kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #21116 from wawa0210/enhance-terminationmessage-size 

Added description about the size of terminationMessage file
This commit is contained in:
Kubernetes Prow Robot 2020-06-06 05:21:45 -07:00 committed by GitHub
parent 0909848f1e 425e0a8871
commit 409243673d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
content/en/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
View File

@ -82,6 +82,11 @@ value of `/dev/termination-log`. By customizing this field, you can tell Kuberne
to use a different file. Kubernetes use the contents from the specified file to 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. 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`.
You cannot set the termination message path after a Pod is launched
In the following example, the container writes termination messages to In the following example, the container writes termination messages to
`/tmp/my-log` for Kubernetes to retrieve: `/tmp/my-log` for Kubernetes to retrieve: