# ECK - coordinating nodes expose ingress **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [October 11, 2023, 2:15pm UTC](https://discuss.elastic.co/t/eck-coordinating-nodes-expose-ingress/344830 "2023-10-11T14:15:25Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![octav](https://avatars.discourse-cdn.com/v4/letter/o/5e9695/32.png) [@octav](https://discuss.elastic.co/u/octav)\ **Post date:** [October 11, 2023, 2:15pm UTC](https://discuss.elastic.co/t/eck-coordinating-nodes-expose-ingress/344830/1 "2023-10-11T14:15:26Z")
Hello, We are using ECK for ELK clusters and we have a deployment for example with the following: ```auto - 3 master nodes - 3 data nodes - 2 coordinating nodes ``` When we deploy this, a default `service - -es-http` is created which balances traffic across all nodes. We are exposing this service via ingress where we are using the `-es-http` service created earlier. When we do a curl to this ingress: `https://mycluster` we can see that the requests are balanced on EVERY node. However, when performing data injection via the ingress created earlier, how to actually check that the requests are actually going only to the coordinating nodes? because they are like smart LoadBalancers . Only this type of nodes should receive indexing requests? This default creation of service and using it for an ingress automatically does this? I need to expose just the coordinating nodes or use the default service? Looking forward, Octavian ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 8, 2023, 2:15pm UTC](https://discuss.elastic.co/t/eck-coordinating-nodes-expose-ingress/344830/2 "2023-11-08T14:15:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.