# Load balancing using svc.cluster.local

**URL:** <https://discuss.kubernetes.io/t/load-balancing-using-svc-cluster-local/21109>\
**Category:** General Discussions\
**Created:** [August 28, 2022, 4:23am UTC](https://discuss.kubernetes.io/t/load-balancing-using-svc-cluster-local/21109 "2022-08-28T04:23:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![AnandKumar](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/anandkumar/32/10712_2.png) [@AnandKumar](https://discuss.kubernetes.io/u/AnandKumar)\
**Post date:** [August 28, 2022, 4:23am UTC](https://discuss.kubernetes.io/t/load-balancing-using-svc-cluster-local/21109/1 "2022-08-28T04:23:44Z")

</div>

We are using svc.cluster.local endpoint to route traffic to another pods but its not happening in load balancing pattern  
Is this expected behaviour ?

---

<div class="post-metadata">

**Author:** ![Theog75](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/theog75/32/9241_2.png) [@Theog75](https://discuss.kubernetes.io/u/Theog75)\
**Post date:** [August 28, 2022, 2:17pm UTC](https://discuss.kubernetes.io/t/load-balancing-using-svc-cluster-local/21109/2 "2022-08-28T14:17:46Z")

</div>

can you please elaborate a bit on what you are trying to achieve?

svc.cluster.local is a domain suffix for infra-cluster FQDNs, but you need to add the namespace and the service name.

---

<div class="post-metadata">

**Author:** ![AnandKumar](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/anandkumar/32/10712_2.png) [@AnandKumar](https://discuss.kubernetes.io/u/AnandKumar)\
**Post date:** [August 28, 2022, 3:00pm UTC](https://discuss.kubernetes.io/t/load-balancing-using-svc-cluster-local/21109/3 "2022-08-28T15:00:50Z")

</div>

Hi @Theog75

From one of the pod we are calling another endpoint which is internal to cluster

Pod 1 → svc-one..svc.cluster.local

we checked logs of pod of svc-one, but request are not coming in distributed fashion.

---

<div class="post-metadata">

**Author:** ![Theog75](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/theog75/32/9241_2.png) [@Theog75](https://discuss.kubernetes.io/u/Theog75)\
**Post date:** [August 28, 2022, 3:15pm UTC](https://discuss.kubernetes.io/t/load-balancing-using-svc-cluster-local/21109/4 "2022-08-28T15:15:15Z")

</div>

so the requests are coming but not balanced? if this is the case it is worth mentioning that the LB mechanism of k8s services is “random” (see [Service | Kubernetes](https://kubernetes.io/docs/concepts/services-networking/service/))

> By default, kube-proxy in iptables mode chooses a backend at random.

---

<div class="post-metadata">

**Author:** ![thockin](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/thockin/32/2457_2.png) [@thockin](https://discuss.kubernetes.io/u/thockin)\
**Post date:** [August 28, 2022, 3:32pm UTC](https://discuss.kubernetes.io/t/load-balancing-using-svc-cluster-local/21109/5 "2022-08-28T15:32:21Z")

</div>

Be aware: It load-balances on CONNECTIONs not REQUESTS. If you have an HTTP client which reuses connections, you will not see load-balancing.