You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 25, 2021. It is now read-only.
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”.
Part of this is to disentangle binderhub from the current setup wrt kubernetes - particularly the helm chart. Binderhub's architecture makes this quite possible.
jupyterhub/binderhub#1318 will be a start, making kubernetes a soft dependency of binderhub. This will also help extract functionality that's in the helm chart that doesn't need to be.
The text was updated successfully, but these errors were encountered:
From https://discourse.pangeo.io/t/notes-from-the-pangeo-2i2c-kick-off-meeting/1587,
Part of this is to disentangle binderhub from the current setup wrt kubernetes - particularly the helm chart. Binderhub's architecture makes this quite possible.
jupyterhub/binderhub#1318 will be a start, making kubernetes a soft dependency of binderhub. This will also help extract functionality that's in the helm chart that doesn't need to be.
The text was updated successfully, but these errors were encountered: