deploy, manifests: enable cloud storage volume expansion & label local volume (#772) #781
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
|
/run-e2e-in-kind |
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.
cherry-pick #772 to release-1.0
What problem does this PR solve?
What is changed and how does it work?
Cloud storage volume expansion is enabled by default. Hostname label will be attached to local PV.
Check List
Tests
allowVolumeExpansionattribute can be updated in-place bykubectl edit sc ebs-gp2to addallowVolumeExpansion: trueallowVolumeExpansion: true, updating PVC with larger storage size, the corresponding PV will be expanded to the desired size.reclaimPolicycan not be changed dynamically. So old gke persistent disk storage class cannot migrate toRetain.Code changes
Side effects
None
Related changes
Does this PR introduce a user-facing change?: