You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was experimenting with the --wait=all command and found the that implementation grabs a list of the pods and then waits for them to be healthy, however, sometimes the list of pods is pulled before some of the pods have even been created, resulting in them not being in the waiting check. For example I had a run where the wait returned quickly, but after running kubectl get pods -A I could see that the coredns pod was just created and was not ready.
The text was updated successfully, but these errors were encountered:
I was experimenting with the
--wait=all
command and found the that implementation grabs a list of the pods and then waits for them to be healthy, however, sometimes the list of pods is pulled before some of the pods have even been created, resulting in them not being in the waiting check. For example I had a run where the wait returned quickly, but after runningkubectl get pods -A
I could see that the coredns pod was just created and was not ready.The text was updated successfully, but these errors were encountered: