# Enterprise Search configuration parameters in YAML not applied by ECK

**URL:** <https://discuss.elastic.co/t/enterprise-search-configuration-parameters-in-yaml-not-applied-by-eck/328314>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [March 23, 2023, 7:14am UTC](https://discuss.elastic.co/t/enterprise-search-configuration-parameters-in-yaml-not-applied-by-eck/328314 "2023-03-23T07:14:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebastianboelling](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@sebastianboelling](https://discuss.elastic.co/u/sebastianboelling)\
**Post date:** [March 23, 2023, 7:14am UTC](https://discuss.elastic.co/t/enterprise-search-configuration-parameters-in-yaml-not-applied-by-eck/328314/1 "2023-03-23T07:14:31Z")

</div>

Hi,

I am trying to define configuration parametes in the `config:` section in the YAML file for Enterprise Search and they seem not to be applied by ECK. I am running my own on-premise Kubernetes Cluster and Enterprise Search 8.6.1.

It is described at [Configuration | Elastic Cloud on Kubernetes [2.6] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-enterprise-search-configuration.html) how to do this. On that page it is described that the configuration parameters for Enterprise Search [Configuration | Elastic Enterprise Search documentation [8.6] | Elastic](https://www.elastic.co/guide/en/enterprise-search/current/configuration.html#configuration) must be set in the config: section of the YAML.

I am trying to set **connector.crawler.http.user\_agent: Enterprise-Search-Crawler**

The full YAML would be:

```auto
apiVersion: enterprisesearch.k8s.elastic.co/v1
kind: EnterpriseSearch
metadata:
  name: enterprise-search-quickstart
spec:
  version: 8.6.2
  count: 1
  elasticsearchRef:
    name: quickstart
  config:
    ent_search.external_url: https://my-custom-domain:3002
    kibana.host: https://kibana.my-custom-domain:5601
    connector.crawler.http.user_agent: Enterprise-Search-Crawler

```

If I start the POD by kubectl it will start and run without any problems. The configs for ent\_search.external\_url and kibana.host seem to be applied but no other config parameters...

What I am doing wrong? Is this the correct way or should it work in that way and its an problem with my environment?`

Regards

Sebastian

---

<div class="post-metadata">

**Author:** ![Jennifer\_Klemisch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jennifer_klemisch/32/116059_2.png) [@Jennifer\_Klemisch](https://discuss.elastic.co/u/Jennifer_Klemisch)\
**Post date:** [April 4, 2023, 6:26pm UTC](https://discuss.elastic.co/t/enterprise-search-configuration-parameters-in-yaml-not-applied-by-eck/328314/2 "2023-04-04T18:26:50Z")

</div>

Any progress on this? I'm running into similar issues.

---

<div class="post-metadata">

**Author:** ![sebastianboelling](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@sebastianboelling](https://discuss.elastic.co/u/sebastianboelling)\
**Post date:** [April 5, 2023, 7:31am UTC](https://discuss.elastic.co/t/enterprise-search-configuration-parameters-in-yaml-not-applied-by-eck/328314/3 "2023-04-05T07:31:15Z")

</div>

Hi,  
I've got the information from the Elastic Support to use `crawler.http.user_agent` instead for Elastic Crawler or App Search Crawler. For me it worked. Seems to be a bug. The will fix it.  
Regards

---

<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:** [May 3, 2023, 7:32am UTC](https://discuss.elastic.co/t/enterprise-search-configuration-parameters-in-yaml-not-applied-by-eck/328314/4 "2023-05-03T07:32:15Z")

</div>

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