Properly annotate OpenStack PVs on CCM/CSI migration #1482
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.
What this PR does / why we need it:
As per the OpenStack CCM/CSI migration guide, all PersistentVolumes created with in-tree OpenStack plugin should be re-annotated with
pv.kubernetes.io/provisioned-by=cinder.csi.openstack.org
annotation.I've researched and found out that volumes created with the in-tree OpenStack plugin have
pv.kubernetes.io/provisioned-by=kubernetes.io/cinder
annotation, so I use that annotation to find PVs that should be patched with a new annotation.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1452
Does this PR introduce a user-facing change?: