# Deployment of Elasticsearch to EKS cluster with helm

**URL:** <https://discuss.elastic.co/t/deployment-of-elasticsearch-to-eks-cluster-with-helm/323944>\
**Category:** Elasticsearch\
**Created:** [January 25, 2023, 3:38pm UTC](https://discuss.elastic.co/t/deployment-of-elasticsearch-to-eks-cluster-with-helm/323944 "2023-01-25T15:38:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Boris\_Tsekinovsky](https://avatars.discourse-cdn.com/v4/letter/b/51bf81/32.png) [@Boris\_Tsekinovsky](https://discuss.elastic.co/u/Boris_Tsekinovsky)\
**Post date:** [January 25, 2023, 3:38pm UTC](https://discuss.elastic.co/t/deployment-of-elasticsearch-to-eks-cluster-with-helm/323944/1 "2023-01-25T15:38:37Z")

</div>

Hello elastic community,

I'm trying to install ELK stack on AWS EKS cluster. I've created the cluster using CDK and now trying to deploy elasticsearch using helm:

```auto
helm install elasticsearch elastic/elasticsearch -n monitoring -f values.yaml --set replicas=1

```

While my values.yaml is like:

```auto
---
# Permit co-located instances for solitary minikube virtual machines.
antiAffinity: "soft"

# Shrink default JVM heap.
esJavaOpts: "-Xmx512m -Xms512m"

# Allocate smaller chunks of memory per pod.
resources:
  requests:
    cpu: "100m"
    memory: "512M"
  limits:
    cpu: "1000m"
    memory: "512M"

# Request smaller persistent volumes.
volumeClaimTemplate:
  accessModes: ["ReadWriteOnce"]
  storageClassName: "standard"
  resources:
    requests:
      storage: 10Gi

```

The deployment is successful but elasticsearch pod remains permanently in Pending state:

```auto
(base) ➜ ~ kubectl get pods -n monitoring
NAME READY STATUS RESTARTS AGE
elasticsearch-master-0 0/1 Pending 0 12m
(base) ➜ ~

```

When I run describe option of kubectl I see the following event:

```auto
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Warning FailedScheduling 4m9s default-scheduler running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition

```

Could someone help me to understand what I'm missing?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 25, 2023, 3:49pm UTC](https://discuss.elastic.co/t/deployment-of-elasticsearch-to-eks-cluster-with-helm/323944/2 "2023-01-25T15:49:55Z")

</div>

> [@Boris\_Tsekinovsky](#):
>
> ```auto
> resources:
> requests:
> cpu: "100m"
> memory: "512M"
> limits:
> cpu: "1000m"
> memory: "512M"
> 
> ```

> [@Boris\_Tsekinovsky](#):
>
> ```auto
> # Shrink default JVM heap.
> esJavaOpts: "-Xmx512m -Xms512m"
> 
> ```

Note that the size of the heap should not be larger than 50% of available memory. The smallest heap I have seen used is 512MB, which would require 1GB of RAM for the pod.

---

<div class="post-metadata">

**Author:** ![Boris\_Tsekinovsky](https://avatars.discourse-cdn.com/v4/letter/b/51bf81/32.png) [@Boris\_Tsekinovsky](https://discuss.elastic.co/u/Boris_Tsekinovsky)\
**Post date:** [January 25, 2023, 4:00pm UTC](https://discuss.elastic.co/t/deployment-of-elasticsearch-to-eks-cluster-with-helm/323944/3 "2023-01-25T16:00:53Z")

</div>

I changed the resources memory to `1Gi`. It didn't help. Still see pod in the pending state. I suspect that it could be related to mouning EBS

---

<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:** [February 22, 2023, 4:01pm UTC](https://discuss.elastic.co/t/deployment-of-elasticsearch-to-eks-cluster-with-helm/323944/4 "2023-02-22T16:01:12Z")

</div>

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