Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Select pod resources from binder UI

See original GitHub issue

In the last few weeks, a number of folks have asked for specific resources for specific binders. Examples of these requests are:

can I have a pod with a GPU in it?
can I have a pod with extra memory or CPU?

Kubespawner currently has this functionality through the use of a profile_list.

I’m curious if this is in scope for BinderHub and, if so, what the API would be. I’m imagining a dropdown in the UI that provides the equivalent of the Kubespawner profile list.

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:8 (5 by maintainers)

Top GitHub Comments

2reactions

betatimcommented, Nov 15, 2018

There have been previous discussion on this and one of the questions that keeps coming up is: should the launcher or the creator of a repo control the resource request? What should happen if the request can’t be satisfied (“recommended resources” vs “required resources”)?

From a technical point of view having the repository (the creator) specify it is tricky because it means BinderHub needs to clone the repository in order to find out.

Part of the reason for #712 is that I want to be able to specify resource requests as part of the launch link.

It would be great if you could drive this discussion forwards so that it gets to a point where we have a concrete suggestion to implement that does what people would like it to do.

0reactions

VladimirVisnovskycommented, Mar 29, 2022

Can someone please update the status of this issue?