Re:The Basics: Kubernetes, Mesosphere, and Docker Swarm
by webo on Thursday February 16, 2017 @12:48AM
(#13657986)
You may have misunderstood me. The case I'm talking is, the node reports Ready, but the pod itself is not functioning properly.
One common issue we have is the pod gets stuck in a restart loop (for whatever reason, including starvation of resources). k8s just keeps restarting it for days on that node, instead of simply rescheduling it after X restarts or some other condition.
Re:The Basics: Kubernetes, Mesosphere, and Docker Swarm
by shaklee3 on Thursday February 16, 2017 @01:00AM
(#13658038)
Isn't that what custom liveliness probes are for?
Re:The Basics: Kubernetes, Mesosphere, and Docker Swarm
by webo on Thursday February 16, 2017 @01:12AM
(#13658077)
No- liveness probe just restarts the pod if the check fails, doesn't kill it.
Re:The Basics: Kubernetes, Mesosphere, and Docker Swarm
by amouat on Thursday February 16, 2017 @05:34AM
(#13658899)
I think a failed liveness will restart the container, not the whole pod.
Can you please elaborate this? When you are using replication controllers or deployments, don’t they drive the state to the desired/goal state, which is N replicas of a pod? So when the node is shut down, I guess it should be rescheduling those dead pods somewhere else to satisfy the goal state?