Hi Chris, Thanks for the sending this out. In Magnum, we have already switched to the external provider[1]. The only concern for me now, is the cinder support. Based on understanding, the cinder support in cloud provider openstack is based on CSI. Is it ready for production now? Are there any feature gap between the in-tree and CPO? Thanks. [1] https://github.com/openstack/magnum/commit/6c61a1a949615f6dc1df36f3098cd9746... On 19/07/19 10:46 AM, Chris Hoge wrote:

After speaking with the SIG-Cloud-Provider leadership this week about the status of the in-tree OpenStack provider for Kubernetes, we’ve decided that barring a major blocker we will be removing the code during the 1.17 release cycle. This means that any code that depends on the in-tree provider will not work with the Kubernetes 1.17 release and after.

The in-tree code has been deprecated for over a year now[1], and SIG-OpenStack has maintained an external provider[2] that has moved beyond the in-tree code in features and support.

Old releases of Kubernetes will continue to ship with the OpenStack provider code and work with existing projects. While I would strongly prefer to just remove the code in the 1.16 release, the logistics just aren't feasible.[3]

It's time for us to turn our support fully to the external provider and stop depending on the in-tree code.

Thanks, Chris Hoge SIG-OpenStack and SIG-Cloud-Provider co-lead

[1] https://github.com/kubernetes/kubernetes/pull/63524 [2] https://github.com/kubernetes/cloud-provider-openstack [3] https://github.com/kubernetes/kubernetes/pull/80027

-- Cheers & Best regards, Feilong Wang (王飞龙) -------------------------------------------------------------------------- Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington --------------------------------------------------------------------------