datahub
datahub copied to clipboard
berkeley-dsep-infra
Keeping up with z2jh upgrades
We should have a policy for when and how we will upgrade the JupyterHub chart. We should be pretty up to date as soon as possible, since otherwise long upgrades can get hard.
The mybinder.org project also runs the same chart we do, but at much higher scale. They are also usually on the bleeding edge (I'm also part of that team), and much more so than we can be - almost all the core members of the JupyterHub team are also on the mybinder.org team.
I think what we should do for now is to try and be about 1 month or so behind mybinder.org. So every month at some point, we find out some version mybinder.org was on 3-4 weeks before that, and upgrade to that.
You can see the version that mybinder.org uses by looking at the history of https://github.com/jupyterhub/binderhub/blob/master/helm-chart/binderhub/requirements.yaml. About a month ago, they were on 0.8.0-c83896f - which might actually be older than what we are on? lol.
If mybinder runs on the bleeding edge, then it'd be good if that production testing could inform z2jh as to what is stable. Then that could lead to versioned z2jh releases which would help datahub know what to use.
I am somewhat leery about having a time-delayed sync-ish strategy if we don't know why mybinder is updating. E.g. was it because of a problem, because of a new feature, etc. If we're to keep up to date with git commits and not versioned releases, how do we know what a good commit is? @yuvipanda probably knows, but most orgs don't have one of them. :)
Another option is to just be on the latest released version, and then put pressure on the z2jh JupyterHub community to make more releases quicker :D Not sure which way to go.
I had more conversations with @ryanlovett and am now convinced we should just try and stick to the latest released version instead. We can use the mybinder.org heuristic as a heuristic in the JupyterHub team to make releases more often. I think this is also a more viable long term strategy in figuring out which release to be on :)
Let's not try to upgrade our hub chart until end of semester.
The latest source of truth for what version of jupyterhub that binderhub is running is https://github.com/jupyterhub/binderhub/blob/main/helm-chart/binderhub/Chart.yaml.