-
Notifications
You must be signed in to change notification settings - Fork 55
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
Comments
@mattkelly thanks for pointing out, I will fix it. |
Thanks @andyzhangx! Any chance you can provide a rough ETA for a new image being pushed? |
@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 |
close this issue since I have already implemented following csi drivers which supports k8s v1.12: |
share you the new azure CSI drivers, it's under kubernetes-sig now: You could run those drivers on k8s v1.13.x |
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:
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).
The text was updated successfully, but these errors were encountered: