jupyterhub / team-compass

A repository for team interaction, syncing, and handling meeting notes across the JupyterHub ecosystem.
http://jupyterhub-team-compass.readthedocs.io
62 stars 33 forks source link

scottyhq/jupyter-cloud-scoped-creds adoption by jupyterhub org? #621

Open consideRatio opened 1 year ago

consideRatio commented 1 year ago

I'm interested in maintaining https://github.com/scottyhq/jupyter-cloud-scoped-creds long term, and wanted to ask if @jupyterhub/jupyterhubteam think it sounds good to have it live under the jupyterhub github org. It was originally developed by @scottyhq and @yuvipanda, and they have given approval of the project being adopted by the jupyterhub org.

I figure the project can facilitate and provide documentation to help a jupyterhub user to extract temporary cloud credentials provided to the user server, so that they can for example upload data to an object storage bucket from their own laptop or HPC instance etc. without needing to be granted access to persistent credentials.

In https://github.com/scottyhq/jupyter-cloud-scoped-creds/issues/4 I'm describing a roadmap of things I'd like to work towards and plan to work towards. Overall, I see it as a quite simple project that could benefit many people migrating towards cloud based jupyterhubs to work with larger amounts of data.

I'm especially excited about having a jupyterhub official place to put documentation on providing cloud providers credentials users running k8s pods and how that works. I found it very tricky to understand those mechanisms, and would appreciate having a suitable place to document that. This would involve some demystifying notes about AWS IRSA and GCP workload identity that does complicated things that otherwise could seem like magic when a k8s ServiceAccount has specific annotations on it.

manics commented 1 year ago

What are your thoughts on putting this in a jupyterhub-contrib (or similarly named) GitHub org? https://github.com/jupyterhub/team-compass/issues/519

consideRatio commented 1 year ago

@manics I'm absolutely fine with having it in jupyterhub-contrib either directly or to have it at a later time relocated there if you think that makes sense! My main goal is that there is a neutral place where it can live.