Problem scenario
You ran a kubectl command, but you got an error "timed out waiting for condition". It never worked or suddenly stopped working. What should you do?
Possible Solution #1
Use the -v=9 flag. This will maximize the verbosity of the kubectl command's results.
Possible Solution #2
See why the pod is not being created if it uses a Persistent Volume Claim. Is there a PVC available that it needs?
Maybe a volume attachment needs to be deleted; see this veducate.co.uk posting for more information.
Possible Solution #3
Try the kubectl wait command. For more information, see these postings:
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#wait
https://fabianlee.org/2022/01/27/kubernetes-using-kubectl-to-wait-for-condition-of-pods-deployments-services/
Possible Solution #4
See why the pod is not being created if it uses a webhook.
Is there a necessary webhook that is failing? You may want to view this document if you are using OpenShift.
Admission webhooks can be problematic; see this posting for more information.
If a webhook involved in the creation of a Pod is now blocked by a lack of a route to the destination URL? If routes were changed eliminating a path to the internet or a firewall was recently put in place, can you check the webhooks that may be involved in a container/pod? Is the URL of the webhook up and available like you think it is?
If you want to turn off a validating webhook, see this.
Possible Solution #5
Deploy Kubernetes again. See this StackOverflow explanation.