Fix storage class not being selected properly #10808
Merged
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.
Summary
Fixes #10765
The current logic pre-selects the storage class if a default storage class exists(i.e. it has
annotations: {'storageclass.kubernetes.io/is-default-class': 'true'}
) and no storage class is already set. Two scenarios needed to be addressed:Areas or cases that should be tested
In the summary^.
Areas which could experience regressions
n/a
Screenshot/Video
10765.mov
Checklist