PodReadyToStartContainers condition lacks diagnostic message when pods stuck in ContainerCreating

[harche]

What happened?

When a pod gets stuck in ContainerCreating state, the PodReadyToStartContainers condition is set to False but provides no Message or Reason explaining why the pod sandbox cannot be created. This makes it extremely
difficult for users and operators to understand where in the pod startup process the pod is stuck and what is blocking it.

What did you expect to happen?

The PodReadyToStartContainers condition should include a descriptive Message field explaining why the pod is not ready to start containers, similar to how other pod conditions provide diagnostic information.

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

1. Deploy a pod that will get stuck during sandbox creation (e.g., due to network issues, CNI failures, or resource constraints)
2. Observe the pod status with kubectl describe pod <pod-name> or kubectl get pod <pod-name> -o yaml
3. Note that the PodReadyToStartContainers condition shows Status: False but has no Message field

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

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-sigs/prow repository.

[harche]

/assign
/sig node

xref : https://issues.redhat.com/browse/OCPBUGS-64625