This is not strictly correct though, because a pod can cease to be "ready" but not die. We've intentionally NOT drawn this as a state-machine because conditions are really orthogonal concepts. We report a singular status as part of kubectl, so maybe we should document THAT, but it's more complicated than this diagram captures.
Issues go stale after 30d of inactivity.
Prevent issues from auto-closing with an
If this issue is safe to close now please do so with
Send feedback to sig-testing, kubernetes/test-infra and/or