Add the CSIMigration and CSIMigrationComplete fields to the API #1109
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:
This PR adds the following fields to the v1beta1 API:
CSIMigration
(csiMigration
) - enablesCSIMigration
andCSIMigration{Provider}
feature flags on the API server, kube-controller-manager, and kubelets for providers that support the CSI migrationCSIMigrationAzureDisk
andCSIMigrationAzureFile
feature gates are enabledCSIMigrationComplete
(csiMigrationComplete
) - enables theCSIMigration{Provider}Complete
feature gate for providers that support the CSI migration. Enabling this feature disables fallback to the in-tree volume plugins.CSIMigrationAzureDiskComplete
andCSIMigrationAzureFileComplete
feature gates are enabledThis PR only adds the API fields. The code to enable the appropriate feature gates will be added in a follow-up PR.
This PR also adds a validation rule to ensure that
CSIMigration
is enabled ifCSIMigrationComplete
is enabled. The full config manifest has been updated to include those two fields and the appropriate descriptions.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Relevant to #616
Supersedes #1107
Does this PR introduce a user-facing change?:
/assign @kron4eg
/kind feature api-change