Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSI support for Kubernetes v1.12.x #8

Closed
mattkelly opened this issue Oct 29, 2018 · 5 comments
Closed

CSI support for Kubernetes v1.12.x #8

mattkelly opened this issue Oct 29, 2018 · 5 comments

Comments

@mattkelly
Copy link

mattkelly commented Oct 29, 2018

The way CSIs are registered/operate has fundamentally changed in Kubernetes v1.12.x. This means that the existing images and manifests no longer work:

Events:
  Type     Reason                  Age               From                                              Message
  ----     ------                  ----              ----                                              -------
  Normal   Scheduled               27s               default-scheduler                                 Successfully assigned default/nginx-csi-hostpath to cs-3f10d2ba-bec9-4f75-92fc-bdd571e26633
  Normal   SuccessfulAttachVolume  27s               attachdetach-controller                           AttachVolume.Attach succeeded for volume "kubernetes-dynamic-pv-34d8871adbc411e8"
  Warning  FailedMount             3s (x6 over 19s)  kubelet, cs-3f10d2ba-bec9-4f75-92fc-bdd571e26633  MountVolume.MountDevice failed for volume "kubernetes-dynamic-pv-34d8871adbc411e8" : driver name csi-hostpath not found in the list of registered CSI drivers

You can easily reproduce this by following the steps listed here.

Other CSIs broke in the same way. For example, you can reference the similar DigitalOcean issue that was recently fixed (though the issue itself is not closed yet).

@andyzhangx
Copy link
Collaborator

@mattkelly thanks for pointing out, I will fix it.

@mattkelly
Copy link
Author

Thanks @andyzhangx! Any chance you can provide a rough ETA for a new image being pushed?

@andyzhangx
Copy link
Collaborator

@mattkelly It's not related to the csi-hostpath image, I have followed exactly as https://kubernetes-csi.github.io/docs/Example.html, and it works. There is really big change in v1.12.x, by default, CSI is even not enabled. Anyway, the csi-hostpath works now. And thanks for pointing out, my next major work would write azure disk & azure file csi drivers, make it work on v1.12.x

@andyzhangx
Copy link
Collaborator

close this issue since I have already implemented following csi drivers which supports k8s v1.12:
https://github.com/Azure/kubernetes-volume-drivers/tree/master/csi/azuredisk
https://github.com/Azure/kubernetes-volume-drivers/tree/master/csi/azurefile

@andyzhangx
Copy link
Collaborator

share you the new azure CSI drivers, it's under kubernetes-sig now:
https://github.com/kubernetes-sigs/azuredisk-csi-driver
https://github.com/kubernetes-sigs/azurefile-csi-driver

You could run those drivers on k8s v1.13.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants