<p>I have an app running on three pods behind a loadbalancer, all set up with Kubernetes. My problem is that when I take pods down or update them, this results in a couple of 503s before the loadbalancer notices the pod is unavailable and stops sending traffic to it. Is there any way to inform the loadbalancer directly that it should stop sending traffic to a pod? So we can avoid the 503s on pod update</p>

Peter Lind
<p>You need to keep in mind if the pods are down the loadbalancer will still be redirecting the traffic to the designated service ports, and as no pod is servicing those ports. </p>

<p>Hence you should use rolling update mechanism in kubernetes which gives zero down time to the deployment. <a href="https://kubernetes.io/docs/tasks/run-application/rolling-update-replication-controller/" rel="nofollow noreferrer">link</a></p>
