Open
Description
We provide storage buckets for users to write to and setup credentials for them within the user servers started on the hubs. But, what if they want to upload something to those hubs from their local computer or similar - then how do they acquire permissions to do so?
@scottyhq has developed scottyhq/jupyter-cloud-scoped-creds but that currently has support for AWS S3 buckets but not for GCP buckets.
Work items
- Trial scottyhq/jupyter-cloud-scoped-creds with an AWS S3 bucket
- Figure out how to do the same against GCP buckets
Resovled by Add subcommand for GCP scottyhq/jupyter-cloud-scoped-creds#2 (comment). - Figure out what credentials is extracted, are they temporary or long term?
This should be documented as well, and it would be very good if they are just temporary compared to long term re-usable.
We rely on GCP's workload identity, and AWS's IRSA, which are mechanisms to couple a k8s ServiceAccount with cloud provider credentials.
Resolved by Add subcommand for GCP scottyhq/jupyter-cloud-scoped-creds#2 (comment) - they are "short lived" and valid for one hour. - Upstream the equivalent for GCP buckets
- Document use of scottyhq/jupyter-cloud-scoped-creds for AWS and GCP buckets
- Communicate progress to Julius in https://2i2c.freshdesk.com/a/tickets/387 and Arpita in https://2i2c.freshdesk.com/a/tickets/322
User requests
Maybe related
Related
- scottyhq/jupyter-cloud-scoped-creds adoption by jupyterhub org? jupyterhub/team-compass#621
- Add subcommand for GCP scottyhq/jupyter-cloud-scoped-creds#2
- Allow project to be adopted by the jupyterhub github organization? scottyhq/jupyter-cloud-scoped-creds#4
- Rename to
jupyter-cloud-creds
? scottyhq/jupyter-cloud-scoped-creds#5 - Clear error message and code if
aws
orgcloud
CLI's are missing scottyhq/jupyter-cloud-scoped-creds#6 - Add a endpoint to emit the version etc for use in tests scottyhq/jupyter-cloud-scoped-creds#7
Metadata
Metadata
Assignees
Labels
No labels