vSphere in-tree to CSI driver migration

[davidz627]

Enhancement Description

• One-line enhancement description (can be used as a release note): Migrate the internals of in-tree VSphere Plugin to call out to the VSphere 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): @divyenpatel @xing-yang
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target: 1.18
  • Beta release target (off-by-default): 1.19
  • Beta release target (on-by-default): 1.25
  • Stable release target (x.y): 1.26
• GA
  • PRs
    • Code: Promote CSIMigrationvSphere to GA kubernetes#113336
    • Doc: CSIMigrationvSphere doc update website#37701

Parent enhancement: #625
Public Migration testing CI: LINK

TODO

• Replace design/KEP with specific one if needed
• Link public migration testing CI

[davidz627]

/sig storage

[jeremyrickard]

Hey @davidz627,

I see in the enhancement description you're targeting 1.18 for this. Can you confirm if this will be in 1.18? Enhancement Freeze is about a week away and we'll need to track it now if you'd like to be included? I think in #625 you indicated 1.19 for that one, are these enhancements to track at a more granular level?

Thanks!

[davidz627]

Yes, this is more granular. There is specific integration work required for each in-tree plugin - each of which is gated by a seperate feature flag and graduates at it's own rate based on set criteria. IIUC @divyenpatel and @xing-yang are leading the vSphere storage migration and AFAIK planned a 1.18 alpha so you should confirm with them.

[jeremyrickard]

@davidz627 , as a bit of a process issue, could we get the KEP updated with the actual test plan instead of the statement that just references the design proposal?

[xing-yang]

@jeremyrickard we are still planning 1.18 alpha for vSphere driver. Can you track this please? Thanks.

[jeremyrickard]

@xing-yang yep, we'll track this. The KEP will need to be updated with the actual test plan instead of the reference to the design proposal for us to get it past enhancement freeze though.

cc: @johnbelamaric @alejandrox1 @mrbobbytables

[xing-yang]

Thanks @jeremyrickard! Looks like @davidz627 will update the main KEP with test plan.

[davidz627]

PTAL #1499

[jeremyrickard]

THANK YOU SO MUCH @davidz627

[jeremyrickard]

/milestone v1.18