-
Notifications
You must be signed in to change notification settings - Fork 238
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
Hetzner Cloud: Upgrade CSI driver to 2.0 #2493
Comments
I was reading on hetznercloud/csi-driver#302 which is now in 2.0 and I was wondering, if I have only a basic kubeone cluster in a single region, this issue is not to be concerned when upgrade to Kubeone 1.6 will be possible, considering that hetzner csi 2.0 gets in? |
@madalinignisca As far as I can tell, this issue only concerns multi-region clusters. I don't expect that this will have any effect on single-region clusters. |
Quick note regarding the update. We currently do not recommend users to upgrade to |
@apricote Thank you so much for letting us know! We'll stay on v1.6.0 until the issue is not resolved. |
We just released v2.1.0 of the |
KubeOne v1.6.0 will include Hetzner CSI v2.1.0 (see #2578). |
@xmudrii: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Description of the feature you would like to add / User story
As a user, I would like to be able to use Hetzner Cloud CSI driver v2.0.0, since it includes a number of improvements over v1.6.0, which had not been updated for more than a year.
The text was updated successfully, but these errors were encountered: