# Using different names for services created by the operator

**URL:** <https://discuss.elastic.co/t/using-different-names-for-services-created-by-the-operator/273560>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [May 20, 2021, 3:36pm UTC](https://discuss.elastic.co/t/using-different-names-for-services-created-by-the-operator/273560 "2021-05-20T15:36:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pkaramol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pkaramol/32/22610_2.png) [@pkaramol](https://discuss.elastic.co/u/pkaramol)\
**Post date:** [May 20, 2021, 3:36pm UTC](https://discuss.elastic.co/t/using-different-names-for-services-created-by-the-operator/273560/1 "2021-05-20T15:36:24Z")

</div>

When creating the `Elasticsearch` resource (using ECK), the `http` service from where es is accessible is by default named `esresourcename-es-http`.

Is this configurable?

And in general, are all the options that can be configured in the `Elasticsearch` resource listed somewhere?

**edit** : I guess I can look into the CRD itself, just wondering whether there is a more readable way, thanks.

---

<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:** [May 21, 2021, 3:18am UTC](https://discuss.elastic.co/t/using-different-names-for-services-created-by-the-operator/273560/2 "2021-05-21T03:18:16Z")

</div>

You can also just create your own services that use the labels to expose the nodes

---

<div class="post-metadata">

**Author:** ![Thibault\_Richard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thibault_richard/32/50513_2.png) [@Thibault\_Richard](https://discuss.elastic.co/u/Thibault_Richard)\
**Post date:** [June 1, 2021, 10:05am UTC](https://discuss.elastic.co/t/using-different-names-for-services-created-by-the-operator/273560/3 "2021-06-01T10:05:11Z")

</div>

> When creating the `Elasticsearch` resource (using ECK), the `http` service from where es is accessible is by default named `esresourcename-es-http` .  
> Is this configurable?

No, the name of this service is not configurable, it's always `<cluster_name>-es-http`, but you can define your own service.  
This is especially useful if you are operating an Elasticsearch cluster with [different node types](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html) and want control over which nodes handle which types of traffic. See [Traffic Splitting | Elastic Cloud on Kubernetes [master] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-traffic-splitting.html#k8s-traffic-splitting-by-node-type).

> And in general, are all the options that can be configured in the Elasticsearch resource listed somewhere?

Yes, we generate the documentation for all the custom resources managed by ECK: [API Reference | Elastic Cloud on Kubernetes [2.10] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-api-reference.html).

---

<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:** [June 29, 2021, 10:05am UTC](https://discuss.elastic.co/t/using-different-names-for-services-created-by-the-operator/273560/4 "2021-06-29T10:05:12Z")

</div>

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