This document present as a vendor specific KEP for the parent KEP CSI Migration
This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as as described in its parent KEP. For all other contents, please refer to the parent KEP.
- CSIMigrationGCE
- As describe in CSI Migration,
when this feature flag && the
CSIMigration
is enabled at the same time, all operations related to the in-tree volume pluginkubernetes.io/gce-pd
will be redirect to use the corresponding CSI driver. From a user perspective, nothing will be noticed.
- As describe in CSI Migration,
when this feature flag && the
- InTreePluginGCEUnregister
- This flag technically is not part of CSI Migration design. But it happens to be related and helps with
CSI Migration. The name speaks for itself, when this flag is enabled, kubernetes will not register the
kubernetes.io/gce-pd
as one of the in-tree storage plugin provisioners. This flag standalone can work out of CSI Migration features. - However, when all
InTreePluginGCEUnregister
,CSIMigrationGCE
andCSIMigration
feature flags are enabled at the same time. The kube-controller-manager will skip the feature flag checking on kubelet and treat GCE PD CSI migration as already complete. And directly redirect traffic to CSI driver for all gce pd related operations.
- This flag technically is not part of CSI Migration design. But it happens to be related and helps with
CSI Migration. The name speaks for itself, when this flag is enabled, kubernetes will not register the
Please refer to the CSI Migration Production Readiness Review Questionnaire.
[X] I/we understand the owners of the involved components may require updates to existing tests to make this code solid enough prior to committing the changes necessary to implement this enhancement.
No additional tests are needed, rather the issue is orchestrating CSI driver deployment for prow jobs. This has been complicated by the cloud provider extraction work, which no longer permits cloud provider specific orchestration in the k/k repository. This means that it is not possible to run any test for gce-pd in k/k. All such tests have been moved to the cloud-provider-gcp repo and test infrastructure.
k8s.io/csi-translation-lib/plugins/gce_pd.go
:2022-06-21
-69.7
N/A
sig-storage
Driver: gcepd
: https://testgrid.k8s.io/provider-gcp-presubmits#cloud-provider-gcp-e2e-full&include-filter-by-regex=gcepd
Major milestones in the life cycle of a KEP should be tracked in Implementation History
.
- 2021-09-08 KEP created
Major milestones for GCE PD in-tree plugin CSI migration:
-
1.14
- GCE PD CSI migration to Alpha
-
1.17
- GCE PD CSI migration to Beta, off by default.
-
1.23
- GCE PD CSI migration to Beta, on by default.
-
1.25
- GCE PD CSI migration to GA