Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert pinning helm versions to 2.6 #517

Merged
merged 2 commits into from
Feb 23, 2018
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 6 additions & 11 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,18 +43,13 @@ 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`.

### Helm Version recommendation
#### Troubleshooting

Due to a [severe bug](https://github.com/kubernetes/helm/issues/3275) in helm v2.7 and 2.8,
we currently recommend users stick to helm version 2.6 if possible.
If you run into an error along the lines of `no Ingress with the name "jupyterhub-internal" found`,
then you have run into this bug. You can downgrade helm by:

```bash
curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > install-helm.bash
bash install-helm.bash --version v2.6.2
helm init --upgrade
```
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=<YOUR-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

Expand Down
14 changes: 4 additions & 10 deletions doc/source/setup-helm.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,16 +15,11 @@ terminal:

.. code:: bash

curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > install-helm.bash
bash install-helm.bash --version v2.6.2

curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get | bash

`Alternative methods for helm installation <https://github.com/kubernetes/helm/blob/master/docs/install.md>`_
exist if you prefer to install without using the script.

We highly recommend sticking to version 2.6.2 of helm until this severe
`bug <https://github.com/kubernetes/helm/issues/3275>`_ is fixed.

.. _helm-rbac:

Initialization
Expand Down Expand Up @@ -77,11 +72,10 @@ It should provide output like:

.. code-block:: bash

Client: &version.Version{SemVer:"v2.6.2", GitCommit:"46d9ea82e2c925186e1fc620a8320ce1314cbb02", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.6.2", GitCommit:"46d9ea82e2c925186e1fc620a8320ce1314cbb02", GitTreeState:"clean"}
Client: &version.Version{SemVer:"v2.4.1", GitCommit:"46d9ea82e2c925186e1fc620a8320ce1314cbb02", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.4.1", GitCommit:"46d9ea82e2c925186e1fc620a8320ce1314cbb02", GitTreeState:"clean"}

Make sure you have at least version 2.6.2, but not newer (until
`this bug <https://github.com/kubernetes/helm/issues/3275>`_ is fixed)
Make sure you have at least version 2.4.1!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is now saying that 2.4.1 is okay, but I think 2.7 is the minimum version now?


If you receive an error that the Server is unreachable, do another `helm version`
in 15-30 seconds, and it should display the Server version.
Expand Down