Readiness probe stops too early at eviction about kubernetes HOT 5 OPEN

/sig node

from kubernetes.

/triage accepted
/priority backlog

from kubernetes.

/assign

from kubernetes.

In any case it seems this behavior will leave the pod out of the endpoints #110255 so it does not seem related to #116965

from kubernetes.

I would expect readiness probes to continue to work after a pod is terminated - the ready condition is orthogonal to pod deletion status. Once the ready condition becomes false, the probe can be stopped. If the ready condition is already false, we can stop the probe right away.

External system components can use deletion timestamp to make a decision independent of ready (and historically do), but since we added unreadyEndpoints it is appropriate for kubelet to probe ready status until such a time as the probe returns false (or if the pod never started, etc).

from kubernetes.