Releases: hetznercloud/csi-driver
v2.10.1
⚠️ Removed Feature from v2.10.0
We have reverted a workaround for an upstream issue in the Kubernetes scheduler where nodes without the CSI Plugin (e.g. Robot servers) would still be considered for scheduling, but then creating and attaching the volume fails with no automatic reconciliation of the this error.
Due to variations in the CSI specification implementation, these changes disrupted Nomad clusters, requiring us to revert them. We are actively working on placing this workaround behind a feature flag, allowing Kubernetes users to bypass the upstream issue.
This affects you, if you have set the Helm value allowedTopologyCloudServer in v2.10.0. If you are affected by the Kubernetes upstream issue, we will provide a fix in the next minor version v2.11.0.
Learn more about this in #400 and #771.
Bug Fixes
- reverted NodeGetInfo response as it breaks Nomad clusters (#776)
v2.10.0
2.10.0 (2024-10-29)
Features
- add support & tests for Kubernetes 1.31 (#721) (85035b9)
- allow arbitrary length API tokens (#724) (61c3a0e)
- allow passing mkfs format options via storage class parameters (#747) (4b9aa4e)
- change XFS default options to support older kernels (#747) (4b9aa4e)
- drop tests for Kubernetes 1.27 (#722) (d46a54b)
- force pods with volumes to be scheduled on Cloud servers (#743) (702fe01)
- fstype is directly passed to mkfs: mkfs.<fstype> (#749) (173bf2f)
- support for SELinux mount (#756) (719247e), closes #582
- Support SINGLE_NODE_MULTI_WRITER capability (#725) (cd53c23), closes #327
- swarm: removed workaround support for mock staging/unstaging (#746) (465ec21)