# Deploying elasticsearch 7.4.0 with helm crashlooping on k8s

**URL:** <https://discuss.elastic.co/t/deploying-elasticsearch-7-4-0-with-helm-crashlooping-on-k8s/301876>\
**Category:** Elasticsearch\
**Created:** [April 7, 2022, 1:42pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-7-4-0-with-helm-crashlooping-on-k8s/301876 "2022-04-07T13:42:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![erwa](https://avatars.discourse-cdn.com/v4/letter/e/a9adbd/32.png) [@erwa](https://discuss.elastic.co/u/erwa)\
**Post date:** [April 7, 2022, 1:42pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-7-4-0-with-helm-crashlooping-on-k8s/301876/1 "2022-04-07T13:42:05Z")

</div>

Hi,

I've added the elastic helm repo with:  
helm install Elasticsearch elastic/Elasticsearch

And are trying to install Elasticsearch 7.4.0 single node installation with arguments:

```auto
helm install elasticsearch elastic/elasticsearch \
     --set imageTag=7.4.0 \
     --set replicas=1 \
     --set clusterName=es-cluster\
     --set minimumMasterNodes=1

```

But I am getting startup exception:  
Info

2022-04-07T13:28:57.686249194Z

"stacktrace": ["org.Elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [node.remote\_cluster\_client] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"

How do I proceed for creating a dev cluster with 1 node?

Cheers

---

<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:** [April 7, 2022, 1:42pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-7-4-0-with-helm-crashlooping-on-k8s/301876/2 "2022-04-07T13:42:05Z")

</div>

Elasticsearch 7.4 is [EOL](https://www.elastic.co/support/eol) and no longer supported. Please upgrade ASAP.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [April 7, 2022, 2:47pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-7-4-0-with-helm-crashlooping-on-k8s/301876/3 "2022-04-07T14:47:30Z")

</div>

Hey,

did you see that part of the [docs](https://github.com/elastic/helm-charts):

> We recommend that the Helm chart version is aligned to the version of the product you want to deploy. This will ensure that you are using a chart version that has been tested against the corresponding production version. This will also ensure that the documentation and examples for the chart will work with the version of the product, you are installing.  
> For example, if you want to deploy an Elasticsearch `7.7.1` cluster, use the corresponding `7.7.1` [tag](https://github.com/elastic/helm-charts/tree/7.7.1/elasticsearch/).

I suppose that there is a configuration for the node roles at play that did not exist with that version...

---

<div class="post-metadata">

**Author:** ![erwa](https://avatars.discourse-cdn.com/v4/letter/e/a9adbd/32.png) [@erwa](https://discuss.elastic.co/u/erwa)\
**Post date:** [April 7, 2022, 2:57pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-7-4-0-with-helm-crashlooping-on-k8s/301876/4 "2022-04-07T14:57:54Z")

</div>

I read that, so adding

```auto
helm repo add elastic https://helm.elastic.co

```

Will not suffice? How to add tag?

---

<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 5, 2022, 2:58pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-7-4-0-with-helm-crashlooping-on-k8s/301876/5 "2022-05-05T14:58:40Z")

</div>

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