[need help] updating changelog for v0.8

[choldgraf]

Since we are ready to release v0.8 (#1054) this PR updates the changelog for new features.

It needs help from the jupyterhub team to fill in missing pieces!. Please do this either via "suggested edits" in the GitHub UI, or by pushing directly to my branch.

I've marked areas where we need more information with "TODO".

Once we get it filled out, we can merge and get a move-on with the new version!

cc @jupyterhub/jupyterhubteam @jupyterhub/binder-team

Things I could use help with

• Documenting any upgrade tips / warnings for people coming from v0.7
• Running "upgrade tests" from v0.7 (not sure what this means but @minrk has it in Releasing 0.8 #1054)
• Documenting any breaking changes
• Pushing a v0.8 image to Dockerhub (https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/master/CONTRIBUTING.md#push-built-images-to-dockerhub--bump-version)

[choldgraf]

I have semi arbitrarily picked Richie Benaud for this one, @yuvipanda I hope that's OK!

[manics]

hub.extraConfig: not clear to me whether the old format is deprecated:

• https://zero-to-jupyterhub.readthedocs.io/en/latest/advanced.html?highlight=extraconfig#hub-extraconfig says the old and new formats are supported
• https://zero-to-jupyterhub.readthedocs.io/en/latest/reference.html?highlight=extraconfig#custom only has the new format
• If you use the old format the hub logs say

hub.extraConfig should be a dict of strings,
but found a single string instead.

The keys can be anything identifying the
block of extra configuration.

Try this instead:

    hub:
      extraConfig:
        myConfig: |

[consideRatio]

The new format allows for multiple extraConfig entries as a dict can be merged by Helm, while a string cant.

So, let's add a deprecation note in the changelog?

[choldgraf]

I added a few more features using @consideRatio's excellent summary from #841. I also added the contributor list. Edits / additions / subtractions / reorgs are welcome!

[minrk]

@consideRatio

So, let's add a deprecation note in the changelog?

There is a deprecation note in the changelog when this was deprecated (0.6). What's changed in 0.8 is that users are now notified when they use the deprecated configuration. I updated the deprecation note in the image to clarify that the config is loaded and a note in the changelog that the deprecation warnings and validation errors are a new feature.

[minrk]

I added a few more notes for things I found, and some upgrade and troubleshooting steps. I think we're in pretty good shape for making a beta release tomorrow.

[consideRatio]

Related to this, is an issue that is not yet resolved I think: jupyterhub/kubespawner#223

[consideRatio]

In summary, I recall that whenever a user is evicted, as they are from preemptible node pools that run out of their usage time for some reason, they will not be able to login again without a hub-pod restart.

[minrk]

I don't think that's something we should look at for this release. Do you think this means we should not recommend looking at preemptible nodes for now?

[minrk]

commented out the recommendation for now

[consideRatio]

Yeah, I would not recommend them until one of us have successfully utilized them with users that authenticate regularly etc. I ended up with trouble doing it.

I wrote this before I learned about these issues.

[consideRatio]

@minrk this is excellent!!

This LGTM!

[minrk]

OK! Let's hit the button and make the beta. This PR updates the version in the docs to install the beta, so just building and publishing the tag should do it.

[minrk]

ok, published 0.8.0-beta.1 (I forgot that helm doesn't accept Python semver-style 0.8.0b1)