# Helm chart installation fails due to timed out waiting for the condition

**URL:** <https://discourse.jupyter.org/t/helm-chart-installation-fails-due-to-timed-out-waiting-for-the-condition/7269>\
**Category:** JupyterHub\
**Tags:** how-to, help-wanted\
**Created:** [December 27, 2020, 9:59am UTC](https://discourse.jupyter.org/t/helm-chart-installation-fails-due-to-timed-out-waiting-for-the-condition/7269 "2020-12-27T09:59:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vanthome](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/vanthome/32/3327_2.png) [@vanthome](https://discourse.jupyter.org/u/vanthome)\
**Post date:** [December 27, 2020, 9:59am UTC](https://discourse.jupyter.org/t/helm-chart-installation-fails-due-to-timed-out-waiting-for-the-condition/7269/1 "2020-12-27T09:59:28Z")

</div>

I’m trying to install the chart but it fails after a while with:

```
COMBINED OUTPUT:
  Release "jhub" does not exist. Installing it now.
  Error: release jhub failed, and has been uninstalled due to atomic being set: timed out waiting for the condition

```

It’s not that the containers aren’t pulled, they are all there.

The only suspicious thing I see in Kubernetes is:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/jupyter/original/2X/4/45b91bcc79c320287a848d4188ab3c2583223366.png)

But in the logs of the containers I cannot see anything.  
Any idea what condition it could be?

---

<div class="post-metadata">

**Author:** ![manics](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/manics/32/85_2.png) [@manics](https://discourse.jupyter.org/u/manics)\
**Post date:** [December 27, 2020, 5:14pm UTC](https://discourse.jupyter.org/t/helm-chart-installation-fails-due-to-timed-out-waiting-for-the-condition/7269/2 "2020-12-27T17:14:48Z")

</div>

What makes you think it’s _not_ the LoadBalancer that’s causing Helm to report it’s failed?

If you think the timeout is too short you can pass other parameters to Helm. If you don’t have access to a LoadBalancer you could use an Ingress, or a NodePort. If you paste your configuration file here, give us full details about your Kubernetes cluster, and show us your helm command, it’ll be easier for people to help you.

---

<div class="post-metadata">

**Author:** ![vanthome](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/vanthome/32/3327_2.png) [@vanthome](https://discourse.jupyter.org/u/vanthome)\
**Post date:** [December 28, 2020, 9:28pm UTC](https://discourse.jupyter.org/t/helm-chart-installation-fails-due-to-timed-out-waiting-for-the-condition/7269/3 "2020-12-28T21:28:05Z")

</div>

I have changed it to:

```
proxy:
  service:
    type: ClusterIP

```

and now it works. Thanks