# Enterprise Search Pods Fail to Create - Readiness Probe Fails

**URL:** <https://discuss.elastic.co/t/enterprise-search-pods-fail-to-create-readiness-probe-fails/288176>\
**Category:** Elastic Search\
**Created:** [November 1, 2021, 10:23pm UTC](https://discuss.elastic.co/t/enterprise-search-pods-fail-to-create-readiness-probe-fails/288176 "2021-11-01T22:23:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![thomasrice](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@thomasrice](https://discuss.elastic.co/u/thomasrice)\
**Post date:** [November 1, 2021, 10:23pm UTC](https://discuss.elastic.co/t/enterprise-search-pods-fail-to-create-readiness-probe-fails/288176/1 "2021-11-01T22:23:53Z")

</div>

Hello,  
I am having some issues deploying Enterprise Search into my K8's cluster.

I already have Elasticsearch & Kibana working via the crd & operator files:  
[https://download.elastic.co/downloads/eck/1.8.0/crds.yaml](https://download.elastic.co/downloads/eck/1.8.0/crds.yaml)  
[https://download.elastic.co/downloads/eck/1.8.0/operator.yaml](https://download.elastic.co/downloads/eck/1.8.0/operator.yaml)

Now I am trying to deploy Enterprise Search with the following template:

```auto
apiVersion: enterprisesearch.k8s.elastic.co/v1
kind: EnterpriseSearch
metadata:
  name: enterprise-search-example
spec:
  version: 7.15.1
  count: 1
  elasticsearchRef:
    # Name of Elastic Deployment
    name: elastic

```

I see this message when I deploy & the pods fail to start due to it:  
"timestamp": "2021-11-01T22:18:57+00:00", "message": "readiness probe failed", "curl\_rc": "7"

Would anyone have any suggestions?

---

<div class="post-metadata">

**Author:** ![thomasrice](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@thomasrice](https://discuss.elastic.co/u/thomasrice)\
**Post date:** [November 1, 2021, 10:38pm UTC](https://discuss.elastic.co/t/enterprise-search-pods-fail-to-create-readiness-probe-fails/288176/2 "2021-11-01T22:38:12Z")

</div>

To follow up,  
The logs from the service are this:  
Invalid config file (/usr/share/enterprise-search/config/enterprise-search.yml):  
The setting '#/Elasticsearch/host' must use https if '#/Elasticsearch/ssl/enabled' is 'true', but the given value is '[http://elastic-es-http.elastic.svc:9200](http://elastic-es-http.elastic.svc:9200)'

Is there a way to fix this?

---

<div class="post-metadata">

**Author:** ![ross.bell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross.bell/32/77559_2.png) [@ross.bell](https://discuss.elastic.co/u/ross.bell)\
**Post date:** [November 1, 2021, 10:48pm UTC](https://discuss.elastic.co/t/enterprise-search-pods-fail-to-create-readiness-probe-fails/288176/3 "2021-11-01T22:48:47Z")

</div>

Hey @thomasrice,

Either the host that serves Elasticsearch needs to do so over `https`, or your Enterprise Search `enterprise-search.yml` needs to specify `elasticsearch.ssl.enabled: false`. Using that configuration is not advised for security reasons, but I understand that may be acceptable in some closed environments.

You can find documentation on config options here: [Configuration | Elastic Enterprise Search Documentation [7.15] | Elastic](https://www.elastic.co/guide/en/enterprise-search/7.15/configuration.html). I hope that helps!

Ross

---

<div class="post-metadata">

**Author:** ![thomasrice](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@thomasrice](https://discuss.elastic.co/u/thomasrice)\
**Post date:** [November 1, 2021, 11:51pm UTC](https://discuss.elastic.co/t/enterprise-search-pods-fail-to-create-readiness-probe-fails/288176/4 "2021-11-01T23:51:53Z")

</div>

Thanks @ross.bell that's really useful!

I'm now getting this message:

```auto
Elasticsearch API key service must be enabled. It is enabled automatically when you configure Elasticsearch to use TLS on the HTTP interface.
Alternatively, you can explicitly enable the setting within Elasticsearch by opening config/elasticsearch.yml and adding:
xpack.security.authc.api_key.enabled: true

```

Do I need to add xpack.security.authc.api\_key.enabled: true  
to my Elasticsearch.yml ? Something like this?

```auto
spec:
  version: 7.15.1
  nodeSets:
  - name: default
    count: 3
    config:
      xpack.security.authc.api_key.enabled: true

```

---

<div class="post-metadata">

**Author:** ![ross.bell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross.bell/32/77559_2.png) [@ross.bell](https://discuss.elastic.co/u/ross.bell)\
**Post date:** [November 2, 2021, 3:49pm UTC](https://discuss.elastic.co/t/enterprise-search-pods-fail-to-create-readiness-probe-fails/288176/5 "2021-11-02T15:49:48Z")

</div>

Yes, you'll want to enable that setting. I'm not able to tell if the snippet you provided is the correct way to do so in your environment, but I don't see anything wrong with it. There are a number of ways to configure Elasticsearch when running in Docker: [Install Elasticsearch with Docker | Elasticsearch Guide [7.15] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#docker-configuration-methods).

---

<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:32am UTC](https://discuss.elastic.co/t/enterprise-search-pods-fail-to-create-readiness-probe-fails/288176/6 "2022-11-04T08:32:54Z")

</div>