search

kubernetes / website

Kubernetes website and documentation repo:
https://kubernetes.io
Creative Commons Attribution 4.0 International
4.44k stars 14.3k forks source link

Improvement for k8s.io/docs/tasks/debug/debug-application/determine-reason-pod-failure/#customizing-the-termination-message #47351

Open quantummixer opened 1 month ago

quantummixer commented 1 month ago

This is a Feature Request

What would you like to be added

Currently in the Customizing the termination message section, couple of examples of literal paths were provided.
The type of path of terminationMessagePath, does it always expect the K8S node path or container mount path or can it support both kinds of path?
The next area of clarity I am seeking is how can I configure the terminationMessagePath to take in variables, so the customized path can look something like: /dev/termination-log_<NAMESPACE>_<PODNAME>_<CONTAINER>.log Or is the data model I should be thinking is: within each terminationMessage (message / log) entry, it already has context attributes such as , , and captured so, /dev/termination-log is just a top-level directory prefix that will be the catch-all for all pods and namespaces' individual termination log files respectively?

Why is this needed Need clarity and example of how to interpret the type of path expected and is the designed Path able to handle the muxing, allowing different pod instances to all write / append termination logs to the same path?

Comments It will be nice to have some actual examples of actual filenames that are produced in the dev/termination-log directory so we can infer the convention of these filenames and the data schema of these termination log entries to work with.
Thank you.

k8s-ci-robot commented 1 month ago

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
sftim commented 1 month ago

/language en