From 72d00c1cd64eb301be3e7dd609ff733316f22648 Mon Sep 17 00:00:00 2001 From: ryanlovett Date: Wed, 31 Jan 2018 11:17:54 -0800 Subject: [PATCH 1/2] Add note about ingress workaround. --- CHANGELOG.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 11cbd127e2..5af3a484b7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -43,6 +43,10 @@ If you are running v0.4 of the chart, you should upgrade to v0.5 first before upgrading to v0.6. You can find out what version you are using by running `helm list`. +#### Troubleshooting + +If your helm upgrade fails due to the error `no Ingress with the name "jupyterhub-internal" found`, you may be experiencing a [helm bug](https://github.com/kubernetes/helm/issues/3275). To workaround this you will need to run `kubectl --namespace= delete ingress jupyterhub-internal` and re-run the helm upgrade. Note that your hub will not be available over https after the ingress object has been deleted up until the deployment completes. + ### New Features #### More secure by default From 1a0933a623b734846aaf9706e899779de93c01c8 Mon Sep 17 00:00:00 2001 From: Chris Holdgraf Date: Wed, 31 Jan 2018 11:26:30 -0800 Subject: [PATCH 2/2] minor edits to changelog --- CHANGELOG.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5af3a484b7..45e10d5825 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -45,7 +45,11 @@ by running `helm list`. #### Troubleshooting -If your helm upgrade fails due to the error `no Ingress with the name "jupyterhub-internal" found`, you may be experiencing a [helm bug](https://github.com/kubernetes/helm/issues/3275). To workaround this you will need to run `kubectl --namespace= delete ingress jupyterhub-internal` and re-run the helm upgrade. Note that your hub will not be available over https after the ingress object has been deleted up until the deployment completes. +If your helm upgrade fails due to the error `no Ingress with the name "jupyterhub-internal" found`, +you may be experiencing a [helm bug](https://github.com/kubernetes/helm/issues/3275). To work +around this, run `kubectl --namespace= delete ingress jupyterhub-internal` and +re-run the `helm upgrade` command. Note that this will cause a short unavailability of your hub +over HTTPS, which will resume normal availability once the deployment upgrade completes. ### New Features