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
Currently if a pod is unresponsive, some other user/client may have to explicitly issue a pod delete to reboot it. This is standard practice for statefulset pods and there are reasons that K8s doesn't just always automatically restart a pod on a new host. However we need to think about whether we should support optional policies for automated pod restart, specifiable in the app CR and/or cluster CR.
The text was updated successfully, but these errors were encountered:
Currently if a pod is unresponsive, some other user/client may have to explicitly issue a pod delete to reboot it. This is standard practice for statefulset pods and there are reasons that K8s doesn't just always automatically restart a pod on a new host. However we need to think about whether we should support optional policies for automated pod restart, specifiable in the app CR and/or cluster CR.
The text was updated successfully, but these errors were encountered: