<p>I am new to Kubernetes.
If there is any service deployed using EKS having 4 replicas A,B,C,D.
Usually loadbalancer directs requests to these replicas
But if I want that my request should go to replica A only or B only...
How can we achieve it.
Request to share some links or steps for guidance</p>

<p>What you could use are the <a href="https://kubernetes.io/docs/concepts/services-networking/service/#headless-services" rel="nofollow noreferrer">Headless Services</a>:</p>
<blockquote>
<p>Sometimes you don't need load-balancing and a single Service IP. In
this case, you can create what are termed &quot;headless&quot; Services, by
explicitly specifying <code>&quot;None&quot;</code> for the cluster IP (<code>.spec.clusterIP</code>).</p>
<p>You can use a headless Service to interface with other service
discovery mechanisms, without being tied to Kubernetes'
implementation.</p>
<p>For headless <code>Services</code>, a cluster IP is not allocated, kube-proxy
does not handle these Services, and there is no load balancing or
proxying done by the platform for them. How DNS is automatically
configured depends on whether the Service has selectors defined:</p>
<ul>
<li>With selectors</li>
</ul>
<p>For headless Services that define selectors, the endpoints controller
creates Endpoints records in the API, and modifies the DNS
configuration to return records (addresses) that point directly to the
<code>Pods</code> backing the <code>Service</code>.</p>
<ul>
<li>Without selectors</li>
</ul>
<p>For headless Services that do not define selectors, the endpoints
controller does not create <code>Endpoints</code> records. However, the DNS
system looks for and configures either:</p>
<ul>
<li><p>CNAME records for <a href="https://kubernetes.io/docs/concepts/services-networking/service/#externalname" rel="nofollow noreferrer">ExternalName</a>-type Services.</p>
</li>
<li><p>A records for any <code>Endpoints</code> that share a name with the Service, for all other types.</p>
</li>
</ul>
</blockquote>
<p>So, a <code>Headless service</code> is the same as default <code>ClusterIP service</code>, but without  load balancing or proxying and therefore allowing you to connect to a Pod directly.</p>
<p>You can also reference below guides for further assistance:</p>
<ul>
<li><p><a href="https://dev.to/kaoskater08/building-a-headless-service-in-kubernetes-3bk8" rel="nofollow noreferrer">Building a headless service in Kubernetes</a></p>
</li>
<li><p><a href="https://medium.com/faun/kubernetes-headless-service-vs-clusterip-and-traffic-distribution-904b058f0dfd" rel="nofollow noreferrer">Kubernetes Headless service vs ClusterIP and traffic distribution</a></p>
</li>
</ul>
