# Expose the http service only for ingest nodes in ECK 2.6.1

**URL:** <https://discuss.elastic.co/t/expose-the-http-service-only-for-ingest-nodes-in-eck-2-6-1/324990>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Tags:** docker\
**Created:** [February 8, 2023, 9:37am UTC](https://discuss.elastic.co/t/expose-the-http-service-only-for-ingest-nodes-in-eck-2-6-1/324990 "2023-02-08T09:37:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![screwyy](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@screwyy](https://discuss.elastic.co/u/screwyy)\
**Post date:** [February 8, 2023, 9:37am UTC](https://discuss.elastic.co/t/expose-the-http-service-only-for-ingest-nodes-in-eck-2-6-1/324990/1 "2023-02-08T09:37:14Z")

</div>

Hello,

I have a cluster in k8s deployed with ECK 2.6.1 which has 2 ingest nodes.  
How can I control that data sent to the ingest nodes for pre-indexing instead of the whole cluster ?  
I see in the custom resource that `http` is not set per `nodeSets` but at a cluster level.  
So how can I target the ingest nodes other than creating a separate Service resource and use some label at `selector` for ingest nodes ?

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [February 8, 2023, 3:41pm UTC](https://discuss.elastic.co/t/expose-the-http-service-only-for-ingest-nodes-in-eck-2-6-1/324990/2 "2023-02-08T15:41:01Z")

</div>

I don't think u can. You have to make another service with selectors.

---

<div class="post-metadata">

**Author:** ![Ayush\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayush_mathur/32/77134_2.png) [@Ayush\_Mathur](https://discuss.elastic.co/u/Ayush_Mathur)\
**Post date:** [February 8, 2023, 3:55pm UTC](https://discuss.elastic.co/t/expose-the-http-service-only-for-ingest-nodes-in-eck-2-6-1/324990/3 "2023-02-08T15:55:05Z")

</div>

@screwyy you can create a route to your target ingest node similar to how it's done for other services running in a namespace.  
However, do keep in mind that when you have SPOC for ingestion and logging is performed heavily by the services, you will end up in bulk write request rejections (status 429) more frequently.

---

<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:** [March 8, 2023, 3:55pm UTC](https://discuss.elastic.co/t/expose-the-http-service-only-for-ingest-nodes-in-eck-2-6-1/324990/4 "2023-03-08T15:55:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.