-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closed
Labels
sig/storageCategorizes an issue or PR as relevant to SIG Storage.Categorizes an issue or PR as relevant to SIG Storage.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA statusDenotes an issue tracking an enhancement targeted for Stable/GA statustracked/noDenotes an enhancement issue is NOT actively being tracked by the Release TeamDenotes an enhancement issue is NOT actively being tracked by the Release Team
Description
Enhancement Description
- One-line enhancement description (can be used as a release note): Migrate the internals of in-tree GCE PD Plugin to call out to the PD CSI Driver while maintaining the original API
- Design proposal link (community repo): https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/csi-migration.md
- KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/20190129-csi-migration.md
- Primary contact (assignee): @davidz627
- Responsible SIGs: sig-storage
- Enhancement target (which target equals to which milestone):
- Alpha release: 1.14
- Beta release: 1.17
- Stable release target (x.y): 1.19
Parent enhancement: #625
Public Migration testing CI: https://testgrid.k8s.io/provider-gcp-compute-persistent-disk-csi-driver#Migration%20Kubernetes%20Master%20Driver%20Latest
TODO
- Replace design/KEP with specific one if needed
- Not necessary as PD Migration is standard and does not require additional work
- Link public migration testing CI
Metadata
Metadata
Assignees
Labels
sig/storageCategorizes an issue or PR as relevant to SIG Storage.Categorizes an issue or PR as relevant to SIG Storage.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA statusDenotes an issue tracking an enhancement targeted for Stable/GA statustracked/noDenotes an enhancement issue is NOT actively being tracked by the Release TeamDenotes an enhancement issue is NOT actively being tracked by the Release Team