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

Merge #713 to prod #714

Merged
merged 3 commits into from
May 14, 2019
Merged

Merge #713 to prod #714

merged 3 commits into from
May 14, 2019

Conversation

yuvipanda
Copy link
Contributor

No description provided.

yuvipanda added 3 commits May 13, 2019 21:18
When a user pod starts, we ensure the following GCP
resources:

1. A GCS bucket
2. A Service Account with admin rights on the bucket
3. A Service Account Key for the Service Account

We then populate two environment variables in the
spawned pod

1. SPARK_GCS_BUCKET - name of GCS bucket for this user
2. SPARK_GCS_KEY - JSON Private key for service account

This is all done through a custom Spawner that inherits
from KubeSpawner. This should operate at the level of
a 'Spark+GCS on GCP', so nothing too UCB specific.

In addition, there's a custom role created in the
ucb-datahub-2018 project - projects/ucb-datahub-2018/roles/w261_hub_resource_creator
that has the appropriate permissions needed by the *hub*
to create the resources it needs.
w261: Create cloud resources for users
@yuvipanda yuvipanda merged commit 15f06f0 into prod May 14, 2019
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

Successfully merging this pull request may close these issues.

1 participant