# ECK route/traffic handle

**URL:** <https://discuss.elastic.co/t/eck-route-traffic-handle/236246>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [June 9, 2020, 12:23am UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246 "2020-06-09T00:23:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![guizaols](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guizaols/32/69963_2.png) [@guizaols](https://discuss.elastic.co/u/guizaols)\
**Post date:** [June 9, 2020, 12:23am UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246/1 "2020-06-09T00:23:02Z")

</div>

When I install the ECK operator in my kubernetes cluster it's added a `hulk-es-http` service. I'd like to know if I send all the requests to `https://hulk-es-http:9200` it'll route to the right nodes.

E.g.: 3 master nodes, 2 data/ingest nodes. Will the `hulk-es-http` route all my queries and indexes to the data nodes? Or do I have to create a `hulk-es-data-http` only to handle this?

In case that I have also a **coordinator** node the `hulk-es-http` will send the client requests to the coordinator and it send to the other nodes?

I was reading the docs and the forum but I'm still with these doubts.

Thanks

---

<div class="post-metadata">

**Author:** ![Anya\_Sabo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anya_sabo/32/49903_2.png) [@Anya\_Sabo](https://discuss.elastic.co/u/Anya_Sabo)\
**Post date:** [June 9, 2020, 12:50am UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246/2 "2020-06-09T00:50:11Z")

</div>

I believe [this page](https://www.elastic.co/guide/en/cloud-on-k8s/1.1/k8s-traffic-splitting.html) answers your question, but let us know if you still have questions after that. The [main services page](https://www.elastic.co/guide/en/cloud-on-k8s/1.1/k8s-services.html) has more of an overview as well.

---

<div class="post-metadata">

**Author:** ![guizaols](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guizaols/32/69963_2.png) [@guizaols](https://discuss.elastic.co/u/guizaols)\
**Post date:** [June 9, 2020, 2:36am UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246/3 "2020-06-09T02:36:07Z")

</div>

Thanks for your quickly reply @Anya_Sabo.

Actually I already read theses docs lots of times but I still have the doubt. I'm probably missing some important point. Anyway I'll read again and try to understand better.

---

<div class="post-metadata">

**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\
**Post date:** [June 9, 2020, 7:18am UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246/4 "2020-06-09T07:18:26Z")

</div>

To make it clear just in case:

- the default `<cluster-name>-es-http` services load balances traffic across _all_ nodes
- you can [create your own services](https://www.elastic.co/guide/en/cloud-on-k8s/1.1/k8s-traffic-splitting.html) if you want to route traffic to specific nodes (eg. coordinator nodes, or data nodes, or non-master nodes)

You can also follow [this github issue](https://github.com/elastic/cloud-on-k8s/issues/2572) in which we discuss future plans for improving the default service and/or create other services.

---

<div class="post-metadata">

**Author:** ![guizaols](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guizaols/32/69963_2.png) [@guizaols](https://discuss.elastic.co/u/guizaols)\
**Post date:** [June 9, 2020, 11:39am UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246/5 "2020-06-09T11:39:52Z")

</div>

I got it @sebgl! I think for now the default service would fit to my case.

Just one more thing. Is it better to avoid hits to the master node?  
Eg: my Rails application who index and search documents should point to a exclusive `data-node-http` service to avoid `master node` hits?

---

<div class="post-metadata">

**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\
**Post date:** [June 9, 2020, 12:03pm UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246/6 "2020-06-09T12:03:35Z")

</div>

> Is it better to avoid hits to the master node?

It is better for performance reasons, yes. If your cluster is not under high pressure it may not matter that much.

---

<div class="post-metadata">

**Author:** ![guizaols](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guizaols/32/69963_2.png) [@guizaols](https://discuss.elastic.co/u/guizaols)\
**Post date:** [June 9, 2020, 1:15pm UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246/7 "2020-06-09T13:15:47Z")

</div>

Thanks a lot for your explanation @sebgl. You clarified a lot of doubts I had about the service orchestration 👍

Cheers!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 8:01am UTC](https://discuss.elastic.co/t/eck-route-traffic-handle/236246/8 "2022-11-04T08:01:39Z")

</div>


