# Automating ES installation with ECK via Helm

**URL:** <https://discuss.elastic.co/t/automating-es-installation-with-eck-via-helm/205335>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [October 25, 2019, 11:24pm UTC](https://discuss.elastic.co/t/automating-es-installation-with-eck-via-helm/205335 "2019-10-25T23:24:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aravind](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aravind/32/45644_2.png) [@Aravind](https://discuss.elastic.co/u/Aravind)\
**Post date:** [October 25, 2019, 11:24pm UTC](https://discuss.elastic.co/t/automating-es-installation-with-eck-via-helm/205335/1 "2019-10-25T23:24:13Z")

</div>

I would like to automate the installation of Elasticsearch via ECK on a cloud provider via helm.

I don't want to prematurely go and install the custom kubernetes resource of `kind: Elasticsearch` before the operator is fully initialized and running.

So my question is what guarantees `ECK` is fully up and running ? Asking this so that I could test for that before proceeding to install `Elasticsearch`

Appreciate any response.

---

<div class="post-metadata">

**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\
**Post date:** [October 28, 2019, 5:51am UTC](https://discuss.elastic.co/t/automating-es-installation-with-eck-via-helm/205335/2 "2019-10-28T05:51:55Z")

</div>

Hey @Aravind,

You can probably check the readiness status of ECK StatefulSet. When deployed in the default `elastic-system` namespace, you can retrieve the number of replicas ready with:

```auto
kubectl get statefulset elastic-operator -n elastic-system --template='{{.status.readyReplicas}}'

```

If it returns `1`, then it means the single Pod of this StatefulSet is ready, which means ECK itself is ready.

By the way, it is safe to deploy any Elasticsearch resource even though ECK is not deployed or running, as long as the CRD manifests are deployed. ECK will just pick-up any Elasticsearch resource created beforehand when it starts.

---

<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, 7:31am UTC](https://discuss.elastic.co/t/automating-es-installation-with-eck-via-helm/205335/3 "2022-11-04T07:31:01Z")

</div>