KeyError 'conditions' about pykube HOT 4 CLOSED

+1 . Just ran into this problem as well.
Could it be that the key is actually Condition?
See the object representation at this link, for instance:
kubernetes/kubernetes#8335 (comment)

from pykube.

So I did some more digging. I'm no Golang expert, but this seems to indicate that .status.conditions may be omitted if empty. I think I'd have to read more or bug k8s folks about this to find out more.

from pykube.

Sorry for the spam, but I've been investigating this today on and off.
I asked in the Kubernetes slack and was told the following:

so user creates pod, scheduler assigns pod, kubelet sees pod changed and then updates it to say that it saw it (setting conditions)
between the second and third spot there’s a window (typically a few hundred ms, but could be much longer if the system is loaded)

So it seems to me in most cases it should be ok to simply wait a couple of seconds before updating the pod's status and trying to access the key again.

from pykube.

Fixed in ce140a1

from pykube.