|
| 1 | +# In-tree Storage Plugin to CSI Migration - AWS EBS Design Doc |
| 2 | + |
| 3 | +## Table of Contents |
| 4 | + |
| 5 | +<!-- toc --> |
| 6 | +- [Summary](#summary) |
| 7 | + - [New Feature Gates](#new-feature-gates) |
| 8 | +- [Production Readiness Review Questionnaire](#production-readiness-review-questionnaire) |
| 9 | +- [Implementation History](#implementation-history) |
| 10 | +<!-- /toc --> |
| 11 | + |
| 12 | + |
| 13 | +## Summary |
| 14 | + |
| 15 | +This document present as a vendor specific KEP for the parent KEP |
| 16 | +[CSI Migration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration) |
| 17 | + |
| 18 | +This inherits all the contents from its parent KEP. It will introduce two new feature gates to be |
| 19 | +used as as described in its parent KEP. For all other contents, please refer to the parent KEP. |
| 20 | + |
| 21 | +### New Feature Gates |
| 22 | + |
| 23 | +- CSIMigrationAWS |
| 24 | + - As describe in [CSI Migration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration), |
| 25 | + when this feature flag && the `CSIMigration` is enabled at the same time, the in-tree volume |
| 26 | + plugin `kubernetes.io/aws-ebs` will be redirect to use the corresponding CSI driver. From a |
| 27 | + user perspective, nothing will be noticed. |
| 28 | +- InTreePluginAWSUnregister |
| 29 | + - This flag technically is not part of CSI Migration design. But it happens to be related and helps with |
| 30 | + CSI Migration. The name speaks for itself, when this flag is enabled, kubernetes will not register the |
| 31 | + `kubernetes.io/aws-ebs` as one of the in-tree storage plugin provisioners. This flag standalone |
| 32 | + can work out of CSI Migration features. |
| 33 | + - However, when all `InTreePluginAWSUnregister`, `CSIMigrationAWS` and `CSIMigration` feature |
| 34 | + flags are enabled at the same time. The kube-controller-manager will skip the feature flag checking |
| 35 | + on kubelet and treat AWS EBS CSI migration as already complete. And directly redirect traffic to CSI |
| 36 | + driver for all aws ebs related operations. |
| 37 | + |
| 38 | + |
| 39 | +## Production Readiness Review Questionnaire |
| 40 | + |
| 41 | +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). |
| 42 | + |
| 43 | +## Implementation History |
| 44 | + |
| 45 | +Major milestones in the life cycle of a KEP should be tracked in `Implementation History`. |
| 46 | + |
| 47 | +- 2022-01-08 KEP created |
| 48 | + |
| 49 | +Major milestones for AWS EBS in-tree plugin CSI migration: |
| 50 | + |
| 51 | +- 1.14 |
| 52 | + - AWS EBS CSI migration to Alpha |
| 53 | + |
| 54 | +- 1.17 |
| 55 | + - AWS EBS CSI migration to Beta, off by default. |
| 56 | + |
| 57 | +- 1.23 |
| 58 | + - AWS EBS CSI migration to Beta, on by default. |
| 59 | + |
| 60 | +- 1.24 |
| 61 | + - AWS EBS CSI migration to Stable |
0 commit comments