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

Revisit Globus auth after adding PVC support #262

Open
bodom0015 opened this issue Oct 3, 2018 · 0 comments
Open

Revisit Globus auth after adding PVC support #262

bodom0015 opened this issue Oct 3, 2018 · 0 comments

Comments

@bodom0015
Copy link
Member

bodom0015 commented Oct 3, 2018

Our previous implementation of Globus auth involved writing the user's Globus auth token to a file in their home directory. With the advent of PVC support in Workbench, we no longer have direct filesystem access to this directory from the API server.

We need to find a way to get this auth token to the user within the container.

Some methods proposed:

  1. Put the auth token in a Secret or ConfigMap in the user's namespace - either could then be injected via envvar and/or file into all containers
  2. Run a small Kubernetes Job to write the file to disk - file will be mounted into all containers via the user's PVC
  3. Add an initContainer to each pod/container that the user starts - file will be manually written into all containers upon startup

This issue is complete when we have implemented one of the above or comparable to somehow asynchronously pass the user's Globus auth token from the Workbench apiserver's login handler into the pods that the user subsequently starts.

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

No branches or pull requests

1 participant