Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Run a federation member on the National Research Platform's Nautilus #3222

Open
yuvipanda opened this issue Feb 14, 2025 · 2 comments
Open

Run a federation member on the National Research Platform's Nautilus #3222

yuvipanda opened this issue Feb 14, 2025 · 2 comments

Comments

@yuvipanda
Copy link
Contributor

yuvipanda commented Feb 14, 2025 •
edited
Loading

https://nationalresearchplatform.org/ is an excellent, forward thinking group of people who make kubernetes clusters available for researchers and educational users to use. Docs at https://docs.nationalresearchplatform.org/, and their acceptable use policy is at https://docs.nrp.ai/assets/NRP-AUP.pdf. I'd like to run a mybinder.org federation member there, and the admins there are amenable to it.

It's a big multitenant kubernetes cluster, so there's a bunch of technical things we need to be able to do before we can run there. I think most of those are 'good ideas', and this issue tracks what we'll need to do.

The biggest is probably to stop our dind from running as a privileged daemon. With jupyterhub/repo2docker#1402 we switch to buildkit, which will allow us to do this!
yuvipanda added a commit to yuvipanda/mybinder.org-deploy that referenced this issue Feb 14, 2025
@yuvipanda
Remove unused pd-ssd storageclass + make clusterIssuer optional
296e9e4 
In clusters where there's already a clusterissuer set up, we don't
need to run a cluster issuer ourselves.

Ref jupyterhub#3222
@yuvipanda yuvipanda mentioned this issue Feb 14, 2025
Merged
@yuvipanda
Copy link
Contributor Author

yuvipanda commented Feb 14, 2025 •
edited
Loading

We would also need to stop our dind from being an actual daemonset. It's a daemon right now because we are using hostpath to share the docker socket, which is something I want to move away from too!

@yuvipanda
Copy link
Contributor Author

My overall timeline here is in the order of months, not immediate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yuvipanda