Use pangeo serviceAccount everywhere #613
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This makes us use the `pangeo` Kubernetes ServiceAccount on * singleuser pods * scheduler pods * worker pods Previously, we only used it for worker pods, except for icesat which used it for singleuser & worker. This is in preparation for granting read / write access to a storage bucket to the `pangeo` service account on the cloud backends.
|
Planning to merge this tomorrow. I think we don't want to touch prod the week since the icesat-2 hackweek is running. |
|
Thanks @TomAugspurger - adding the same serviceaccount to all "user-associated" pods seems good to me. Feel free to merge staging and prod. We're using a separate hub for the hackweek over the next two weeks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes us use the
pangeoKubernetes ServiceAccount onPreviously, we only used it for worker pods, except for icesat which
used it for singleuser & worker.
This is in preparation for granting read / write access to a storage
bucket to the
pangeoservice account on the cloud backends.cc @scottyhq @tjcrone. I don't think this requires anything on your end, since the
pangeoKubernetes Service Account should already exist. Do you see any reason not to use it for users / scheduler pods as well?