Potentially lengthy I/O by kubelet during pod startup needs to be visible to the user about kubernetes HOT 3 OPEN

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.

from kubernetes.

/sig node

from kubernetes.

CRI-O users hit this issue and CRI-O emits a metric when pod or container creation is stuck on a specific step for a while. There's currently no better way for the CRI implementation to tell the kubelet what stage a creation request is at now. Having an event would definitely be a better UX

I would say this is (unfortunately) working as intended, as the CRI was not initially designed to have more insight in to the process. That certainly can be redesigned, but it would need a champion to take on the KEP process (and reviewer/approver bandwidth to merge it)

/kind feature
/remove-kind bug

from kubernetes.