# Unable to install dremio helm chart on kubernetes AWS EKS

**URL:** <https://community.dremio.com/t/unable-to-install-dremio-helm-chart-on-kubernetes-aws-eks/3964>\
**Category:** Uncategorized\
**Created:** [August 29, 2019, 5:24pm UTC](https://community.dremio.com/t/unable-to-install-dremio-helm-chart-on-kubernetes-aws-eks/3964 "2019-08-29T17:24:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![meg](https://avatars.discourse-cdn.com/v4/letter/m/35a633/32.png) [@meg](https://community.dremio.com/u/meg)\
**Post date:** [August 29, 2019, 5:24pm UTC](https://community.dremio.com/t/unable-to-install-dremio-helm-chart-on-kubernetes-aws-eks/3964/1 "2019-08-29T17:24:52Z")

</div>

Hello,

I am trying to install dremio on kubernetes AWS eks cluster with below configuration.  
Instancetype: r5.4xlarge which has cpu 16 and memory:128Gib  
NodeAutoScalingGroupMinSize: 1  
NodeAutoScalingGroupMaxSize: 20  
NodeAutoScalingGroupDesiredCapacity: 3

Also,  
In values.yaml below is conf:  
coordinator:  
memory: 100000  
cpu: 2  
count: 0  
web:  
port: 9047  
client:  
port: 31010  
volumeSize: 10Gi  
executor:  
memory: 100000  
cpu: 2  
count: 3  
volumeSize: 10Gi  
zookeeper:  
memory: 1024  
cpu: 0.5  
count: 3  
volumeSize: 10Gi

But dremio is failing to get installed with insufficient memory error.

From resource perspective, this configuration seems to be sufficient.Could you please give some understanding on how this is achievable.

Thanks in Advance!

---

<div class="post-metadata">

**Author:** ![ben](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/ben/32/1367_2.png) [@ben](https://community.dremio.com/u/ben)\
**Post date:** [August 29, 2019, 10:20pm UTC](https://community.dremio.com/t/unable-to-install-dremio-helm-chart-on-kubernetes-aws-eks/3964/2 "2019-08-29T22:20:25Z")

</div>

Hi @meg,

What is the specific error message you are getting? Can you attach the output from your install?

---

<div class="post-metadata">

**Author:** ![Ye\_Li](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/ye_li/32/1672_2.png) [@Ye\_Li](https://community.dremio.com/u/Ye_Li)\
**Post date:** [August 29, 2019, 10:45pm UTC](https://community.dremio.com/t/unable-to-install-dremio-helm-chart-on-kubernetes-aws-eks/3964/3 "2019-08-29T22:45:27Z")

</div>

@meg, can you also do a `kubectl describe nodes` and share the output?

---

<div class="post-metadata">

**Author:** ![meg](https://avatars.discourse-cdn.com/v4/letter/m/35a633/32.png) [@meg](https://community.dremio.com/u/meg)\
**Post date:** [August 30, 2019, 3:31am UTC](https://community.dremio.com/t/unable-to-install-dremio-helm-chart-on-kubernetes-aws-eks/3964/4 "2019-08-30T03:31:40Z")

</div>

Hi,

Good news! I was able to deploy dremio helm chart.  
But still the pods are in pending status.

1. kubectl get nodes  
o/p All nodes are in ready state.  
2.kubectl describe pod dremio-master-0  
o/p : No failed events But Tolerance is as below :  
[node.kubernetes.io/not-ready:NoExecute](http://node.kubernetes.io/not-ready:NoExecute) for 300s  
[node.kubernetes.io/unreachable:NoExecute](http://node.kubernetes.io/unreachable:NoExecute) for 300s

2. $ kubectl get svc  
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE  
dremio-client LoadBalancer ClusterIPiscoming **pending** 31010:32121/TCP,9047:31747/TCP 56m

4.$ kubectl get pod  
NAME READY STATUS RESTARTS AGE  
dremio-executor-0 0/1 Init:0/2 0 56m  
dremio-master-0 0/1 Init:1/4 0 56m

5.$kubectl get services dremio-client  
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE  
dremio-client LoadBalancer CLUSTER-IPiscoming **pending** 31010:32121/TCP,9047:31747/TCP 3m21s

**ISSUE**  
1.External\_IP is in pending state.  
2.POD state for executor and master isnot in running state.  
3.Tolerance shows unreachable or not ready even when nodes are ready.  
Could you please help with this?

Thanks in advance.