Fixing #1300 User-scheduler doesn't work with rancher/local-path-provisioner#1516
Merged
consideRatio merged 1 commit intojupyterhub:masterfrom Dec 4, 2019
Merged
Fixing #1300 User-scheduler doesn't work with rancher/local-path-provisioner#1516consideRatio merged 1 commit intojupyterhub:masterfrom
consideRatio merged 1 commit intojupyterhub:masterfrom
Conversation
Member
|
@cgiraldo thanks this LGTM! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Inspecting the user-schedule-xxxx pod log:
error binding volumes: persistentvolumeclaims "claim-test" is forbidden: User "system:serviceaccount:ns:user-scheduler" cannot update resource "persistentvolumeclaims" in API group "" in the namespace "ns"
I fix it by creating a new roleBinding to let user-scheduler update the volume claim: