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.

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

Allow spawning a namespace per user #76

Open
yuvipanda opened this issue Aug 29, 2017 · 7 comments
Open

Allow spawning a namespace per user #76

yuvipanda opened this issue Aug 29, 2017 · 7 comments

Comments

@yuvipanda
Copy link
Collaborator

@yuvipanda yuvipanda commented Aug 29, 2017

Right now we use one namespace for all user pods. It'll be great to allow spawning one namespace per user, so users can do additional things in their namespaces (like spawning other clusters)

@yuvipanda
Copy link
Collaborator Author

@yuvipanda yuvipanda commented Dec 7, 2017

The biggest problem here is that our reflector only watches one namespace. Should we have multiple watchers? Multiple kinds of watchers?

Perhaps we need a kind of SharedInformer design that lets us hold multiple watchers? Don't want to have one watcher per pod.

@zflamig
Copy link

@zflamig zflamig commented Jun 3, 2018

Is anyone working on this currently? It would be a great feature to have...

@viroos
Copy link

@viroos viroos commented Jun 29, 2018

I will be also interested in having this feature.

@agt
Copy link

@agt agt commented Jun 29, 2018

I'm looking to integrate JupyterHub into an existing k8s cluster which utilizes a large number (>1000) of per-user namespaces.

As discussed in #79 , templating Namespace seems like a reasonable approach. Our namespaces are provisioned externally; would anyone object to deferring ns creation/cleanup to a future enhancement?

@zflamig
Copy link

@zflamig zflamig commented Jun 29, 2018

Based on @yuvipanda's comment, I think those would actually be separate enhancements anyways @agt-ucsd? I think this PR handles the creation/cleanup and then we need to develop a separate one which handles the watching multiple namespaces which is the thing you want?

@agt
Copy link

@agt agt commented Jun 29, 2018

@zflamig thanks, it sounds like you're in agreement that creation/cleanup of per-user namespaces is separable from generic support for multiple user namespaces (which besides converting namespace to a template/callable, would also entail changes to watching). I'll open a separate issue for the latter.

@SolarisYan
Copy link

@SolarisYan SolarisYan commented Jan 29, 2019

@yuvipanda
Hi all, How is this feature going?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants