You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -50,7 +45,7 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
50
45
-[x] (R) Graduation criteria is in place
51
46
-[x] (R) [all GA Endpoints](https://github.com/kubernetes/community/pull/1806) must be hit by [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
52
47
-[x] (R) Production readiness review completed
53
-
-[] (R) Production readiness review approved
48
+
-[x] (R) Production readiness review approved
54
49
-[x] "Implementation History" section is up-to-date for milestone
55
50
-[x] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
56
51
-[x] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
@@ -74,7 +69,7 @@ used as described in its parent KEP. For all other contents, please refer to the
74
69
75
70
## Motivation
76
71
77
-
Currently the Portworx volume provisioning happens through Portworx in-tree driver. As part of the parent KEP [CSI Migration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration), the Portworx in-tree driver needs to be deprecated in order to give to use Portworx CSI driver.
72
+
Currently the Portworx volume provisioning happens through Portworx in-tree driver. As part of the parent KEP [CSI Migration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration), the Portworx in-tree driver logic needs to be "migrated" to use Portworx CSI driver instead.
78
73
79
74
### Goals
80
75
@@ -87,12 +82,12 @@ Currently the Portworx volume provisioning happens through Portworx in-tree driv
87
82
88
83
## Proposal
89
84
90
-
The in-tree to CSI migration feature is already in place in k/k. We just need to enable vendor specific feature gates for it to work for each vendor.
85
+
The in-tree to CSI migration feature is already in place in k/k. We just need to enable Portworx specific feature gates for it to work for Portworx driver.
91
86
92
87
93
88
### Risks and Mitigations
94
89
95
-
- Portworx CSI driver needs to be already deployed in before enabling this feature.
90
+
- Portworx CSI driver needs to be already deployed before enabling this feature.
96
91
97
92
## Design Details
98
93
@@ -142,21 +137,27 @@ N/A
142
137
143
138
* Alpha in 1.23 provided all tests are passing.
144
139
* All functionality is guarded by alpha `CSIMigrationPortworx` feature gate.
140
+
* Portworx CSI migration to Beta, off by default in 1.25. e2e test results are provided in the PR.
145
141
* Beta in 1.31 with design validated by customer deployments
146
142
(non-production)
147
-
* Manual tests with in-tree Portworx volumes
143
+
* Manual testing with in-tree Portworx volumes should be passing.
148
144
* GA in 1.33, with `CSIMigrationPortworx` feature gate graduating to GA.
149
145
150
146
151
147
### Upgrade / Downgrade Strategy
152
148
153
-
N/A
149
+
When `CSIMigrationPortworx` feature gate gets enabled and customers are not using Portworx security feature, the upgrade/downgrade will work without any changes to cluster objects or configurations.
150
+
In case of downgrade, it will revert back to the existing behavior of using in-tree driver.
151
+
152
+
With Portworx security feature enabled, customers will have to add certain annotations to in-tree PVs mentioning the CSI secret name/namespace which the kubelet or CSI sidecar containers can use(using `csi-translation-lib`) to pass secret contents to Portworx CSI driver for operations on in-tree PVs. The annotations to be added will be documented in Portworx documentation.
153
+
The downgrade will work without any changes.
154
154
155
155
### Version Skew Strategy
156
156
157
157
N/A
158
158
159
159
## Production Readiness Review Questionnaire
160
+
Please refer to the [CSI Migration Production Readiness Review Questionnaire](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration#production-readiness-review-questionnaire).
0 commit comments