When creating the Target Pool for Network Load Balance, there is a
health check option.
Also there is a property named
livenessProbe in the container spec.
A liveness probe checks if the container in which it is configured is still running. If the liveness probe fails, the kubelet kills the container, which will be subjected to its restart policy. Set a liveness check by configuring the template.spec.containers.livenessprobe stanza of a pod configuration.
Is the health check needless when the container is configured with
As I understand, if the container is down, POD will be restarted automatically. In this case, no need for health check.
What about the NODE is down? As I understand, kubernetes will start the POD in another NODE, which means the POD will be restarted again.
It seems to me, in any case, health check is needless when livenessProbe is configured.