<p>According to some of the tech blogs (e.g. <a href="https://medium.com/google-cloud/understanding-kubernetes-networking-services-f0cb48e4cc82" rel="nofollow noreferrer">Understanding kubernetes networking: services</a>), k8s service dispatch all the requests through iptable rules.<br>
What if one of the upstream pods crashed when a request happened to be routed on that pods.<br>
Is there a failover mechanism in kubernetes service?<br>
Will the request will be forwarded to next pod  automatically?<br>
How does kubernetes solve this through iptable?</p>

<blockquote>
  <p>Kubernetes offers a simple Endpoints API that is updated whenever the set of Pods in a Service changes. For non-native applications, Kubernetes offers a virtual-IP-based bridge to Services which redirects to the backend Pods</p>
</blockquote>

<p>Here is the detail <a href="https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies" rel="nofollow noreferrer">k8s service &amp; endpoints</a></p>

<p>So your answer is <strong>endpoint Object</strong> </p>

<p><code>kubectl get endpoints,services,pods</code></p>

<p>There are liveness and readiness checks which decides if the pod is able to process the request or not. Kubelet with docker has mechanism to control the life cycle of pods.  If the pod is healthy then its the part of the endpoint object.  </p>
