Skip to content

Commit 0ed2442

Browse files
committed
Address review comments
1 parent 1f9a626 commit 0ed2442

File tree

1 file changed

+12
-11
lines changed
  • keps/sig-storage/2589-csi-migration-portworx

1 file changed

+12
-11
lines changed

keps/sig-storage/2589-csi-migration-portworx/README.md

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,6 @@
88
- [Goals](#goals)
99
- [Non-Goals](#non-goals)
1010
- [Proposal](#proposal)
11-
- [User Stories (Optional)](#user-stories-optional)
12-
- [Story 1](#story-1)
13-
- [Story 2](#story-2)
14-
- [Notes/Constraints/Caveats (Optional)](#notesconstraintscaveats-optional)
1511
- [Risks and Mitigations](#risks-and-mitigations)
1612
- [Design Details](#design-details)
1713
- [Test Plan](#test-plan)
@@ -32,7 +28,6 @@
3228
- [Implementation History](#implementation-history)
3329
- [Drawbacks](#drawbacks)
3430
- [Alternatives](#alternatives)
35-
- [Infrastructure Needed (Optional)](#infrastructure-needed-optional)
3631
<!-- /toc -->
3732

3833
## Release Signoff Checklist
@@ -50,7 +45,7 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
5045
- [x] (R) Graduation criteria is in place
5146
- [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)
5247
- [x] (R) Production readiness review completed
53-
- [] (R) Production readiness review approved
48+
- [x] (R) Production readiness review approved
5449
- [x] "Implementation History" section is up-to-date for milestone
5550
- [x] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
5651
- [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
7469

7570
## Motivation
7671

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.
7873

7974
### Goals
8075

@@ -87,12 +82,12 @@ Currently the Portworx volume provisioning happens through Portworx in-tree driv
8782

8883
## Proposal
8984

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.
9186

9287

9388
### Risks and Mitigations
9489

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.
9691

9792
## Design Details
9893

@@ -142,21 +137,27 @@ N/A
142137

143138
* Alpha in 1.23 provided all tests are passing.
144139
* 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.
145141
* Beta in 1.31 with design validated by customer deployments
146142
(non-production)
147-
* Manual tests with in-tree Portworx volumes
143+
* Manual testing with in-tree Portworx volumes should be passing.
148144
* GA in 1.33, with `CSIMigrationPortworx` feature gate graduating to GA.
149145

150146

151147
### Upgrade / Downgrade Strategy
152148

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.
154154

155155
### Version Skew Strategy
156156

157157
N/A
158158

159159
## 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).
160161

161162
### Feature Enablement and Rollback
162163

0 commit comments

Comments
 (0)