Kubelet (in fact, all components) should be able to log callstack with -log_backtrace_at

[tdihp]

What happened?

See #124313
We made heavy effort n locating a code path which can be done trivially if call stack is available.

Do let me know if reporting this as a bug is appropriate.

What did you expect to happen?

k8s components should all be able to print call stack for a given logging entry.

How can we reproduce it (as minimally and precisely as possible)?

n/a

Anything else we need to know?

No response

Kubernetes version

v1.27.7

Cloud provider

azure

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kundan2707]

/sig cli

[HirazawaUi]

/remove-sig cli
/sig node
/remove-kind bug
/kind feature