Plugin incompatible with CSI 0.2 and upwards

[r2bit]

Since CSI 0.2 brought some breaking changes, this plugin no longer works with latest versions of GoCSI (rexray/gocsi@4c3ac6e).

# /root/go/bin/csc -e unix:///csi.sock identity plugin-info
unknown service csi.v0.Identity

Please use -h,--help for more information

[clintkitson]

Thank you for this @r2bit. VMware is working towards CSI support for K8s 1.12. Please refer to the vSphere cloud provider project for progress towards this driver.

https://github.com/kubernetes/cloud-provider-vsphere

[r2bit]

Thanks for the update, I wasn't aware vSphere provider was being reworked. Going through the docs, it says that both CCM and vsphere-csi will need to connect to vSphere. Does that mean that we're going back to using vSphere API for VMDK management instead of VMCI (like VDVS and current vsphere-csi do)?

[clintkitson]

The current K8s in-tree vSphere provider does not use VMCI like this CSI driver does. The path will be to move away from VMCI for this functionality.

…

On Wed, Jul 18, 2018 at 5:05 AM Janar K ***@***.***> wrote: Thanks for the update, I wasn't aware vSphere provider was being reworked. Going through the docs, it says that both CCM and vsphere-csi will need to connect to vSphere. Does that mean that we're going back to using vSphere API for VMDK management instead of VMCI like VDVS and current vsphere-csi does? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABVMMYH0XMboJNB_mBjNaMEaEh7291Dxks5uHySOgaJpZM4VSmwL> .