<p>If I run</p>
<pre><code>helm upgrade --cleanup-on-fail \
  $RELEASE jupyterhub/jupyterhub \
  --namespace $NAMESPACE \
  --version=0.9.0 \
  --values config.yaml
</code></pre>
<p>It fails, with this error: <code>Error: UPGRADE FAILED: pre-upgrade hooks failed: timed out waiting for the condition</code>. It just hangs for a bit and ultimately times out. It seems like too small of a change to cause a true timeout. I found this command in the Zero to JupyterHub docs, <a href="https://zero-to-jupyterhub.readthedocs.io/en/latest/jupyterhub/customizing/extending-jupyterhub.html#apply-config-changes" rel="nofollow noreferrer">where it describes how to apply changes to the configuration file</a>.</p>
<p>I've tried several permutations, including leaving out cleanup, leaving out version, etc. The only thing I could get to work was <code>helm upgrade jhub jupyterhub/jupyterhub</code>, but I don't think it's producing the desired effect.</p>
<p>For example, when I add a line in my config.yaml to <a href="https://zero-to-jupyterhub.readthedocs.io/en/latest/jupyterhub/customizing/user-environment.html#use-jupyterlab-by-default" rel="nofollow noreferrer">change the default to Jupyter Lab</a>, it doesn't work if I run <code>helm upgrade jhub jupyterhub/jupyterhub</code>. I believe I need to specify config.yaml using --values or -f</p>
<p>My overall project is to set up JupyterHub on a cloud Kubernetes environment. I'm using GKE and the online terminal.</p>
<p>Thanks</p>

Dr. Funkenstein
<p>Solved: I specified <code>tag</code> incorrectly in config.yaml. I put the digest rather than the actual tag. <a href="https://hub.docker.com/r/jupyter/datascience-notebook/tags/?page=1&amp;ordering=last_updated" rel="nofollow noreferrer">Here are the images on DockerHub</a></p>
