NAS-107517 / 20.10 / Setup default storage class for k8s #5653
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
bugclerk
changed the title
sonicaj
changed the title
themylogin
approved these changes
Sep 10, 2020
william-gr
approved these changes
Sep 10, 2020
sonicaj
force-pushed
the
gpu-support
branch
2 times, most recently
from
b12446e
to
8596a92
Compare
sonicaj
force-pushed
the
default-storage-class
branch
from
e4c33aa
to
9b69f02
Compare
This commit adds changes where we setup default storage class for the k8s cluster. Motivation is to allow users freedom to create/update/test workloads manually in their own namespaces which require interaction with persistent volumes.
sonicaj
force-pushed
the
default-storage-class
branch
from
9b69f02
to
5ede62e
Compare
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 commit adds changes where we setup default storage class for the k8s cluster. Motivation is to allow users freedom to create/update/test workloads manually in their own namespaces which require interaction with persistent volumes.