2i2c-org / upstream

A place to keep track of upstream issues that we'd like to work on.
0 stars 0 forks source link

Write proposal for merging binderhub helm-chart (only) into zero to jupyterhub helm chart #45

Open yuvipanda opened 2 years ago

yuvipanda commented 2 years ago

Part of

Remove artificial distinctions between BinderHub/JupyterHub. Currently BinderHub and JupyterHub have strong distinctions between them, but this is not strictly necessary. Binder-like functionality should be a feature flag on any JupyterHub, and thus BinderHub could cease to be a standalone tool, and instead be a “particular configuration of a JupyterHub”.

From https://discourse.pangeo.io/t/notes-from-the-pangeo-2i2c-kick-off-meeting/1587

Implementation details

We want to make sure that others in the community have buy-in for this idea, but it's hard to know exactly what steps would be needed for feedback.

Here is roughly what we want to try:

Updates

choldgraf commented 2 years ago

In a sprint meeting we discussed that this effort is challenging because there are several moving parts, and it's unclear what is the best path to get buy-in from the broader JupyterHub team. We decided that a good next step would be to build a working prototype that shows off image building in JupyterHub deployed as a service via a combined helm chart, to have something specific that we can point to as a benefit, and to help shape discussion with the team. So the order of operations is roughly:

@yuvipanda let me know if any of that looks incorrect