Closed sgibson91 closed 4 years ago
Going to investigate "named servers" to label user pods with the repo name rather than the user's name. This should recover the functionality of an "anonymous" BinderHub and allow the same user to launch the same or different repos in quick succession without having to wait for the culler to remove their pod.
Summary
An authenticated user gets a named pod on the Kubernetes cluster. This mean if they try to relaunch a Binder or launch a new Binder without either:
they will receive the following launch error:
Config below
``` config: BinderHub: use_registry: true image_prefix:https://discourse.jupyter.org/t/binder-failed-to-launch-user-already-has-a-server-running/929
What needs to be done?
Who can help?
Updates