Skip to content

Releases: hetznercloud/csi-driver

v2.22.0

Choose a tag to compare

@hcloud-bot hcloud-bot released this 08 Jul 07:26
2d814c4

Features

  • helm: option to specify service account name for node driver (#1420)

Bug Fixes

  • helm: drop unused secrets get/list permission from controller

v2.21.2

Choose a tag to compare

@hcloud-bot hcloud-bot released this 01 Jun 07:03
22f4b1a

Bug Fixes

  • device needs to be ready on node publish (#1381)

v2.21.1

Choose a tag to compare

@hcloud-bot hcloud-bot released this 20 May 10:15
1dd5776

Bug Fixes

  • chart: prefix local templates to avoid bitnami common collision (#1360)

v2.21.0

Choose a tag to compare

@hcloud-bot hcloud-bot released this 12 May 09:10
d660288

Features

  • support Kubernetes v1.36
  • drop support for Kubernetes v1.32

v2.20.2

Choose a tag to compare

@hcloud-bot hcloud-bot released this 16 Apr 06:33
7c7d75b

Volume Label Truncation Issue

The label value truncation introduced in v2.20.1 could produce values
starting with a non-alphanumeric character (e.g. -), which is invalid
per the https://docs.hetzner.cloud/reference/cloud#description/labels.
Truncated values are now stripped of leading non-alphanumeric characters
to ensure they remain valid.

Bug Fixes

  • strip leading non-alphanumeric characters after truncating volume label (#1328)

v2.20.1

Choose a tag to compare

@hcloud-bot hcloud-bot released this 15 Apr 05:00
bbee911

Validate Volume Labels

With this release, volume labels are validated against Hetzner Cloud API requirements before a volume is created.

To avoid breaking existing setups, label values that exceed the maximum length of 63 characters are automatically truncated from the left, keeping the last 63 characters. This is especially relevant for automatically set labels like pvc-name, pvc-namespace, and pv-name, which may contain long Kubernetes resource names.

Bug Fixes

  • validate hcloud volume labels (#1304)

v2.20.0

Choose a tag to compare

@hcloud-bot hcloud-bot released this 26 Feb 14:17
8ff1f2f

Container Reordering

The hcloud-csi-controller Pod contains multiple containers: one developed by us and several
Kubernetes sidecars. In this release, we reordered the containers so that the hcloud-csi-driver
container now comes first. As a result, it starts first and is selected by default when running
kubectl logs. Previously, the default was the csi-attacher container. If your tooling relies
on this default behavior, please update it accordingly. We made this change to improve
debuggability, especially for newcomers to the ecosystem.

Init Logs

The hcloud-csi-driver container in the hcloud-csi-controller Pod now logs info messages on
startup, including when the default location is selected. Previously, no output was emitted
until the first volume operation was processed. Since location evaluation may involve calls to the
Hetzner Cloud API, these logs should help with debugging networking issues.

Features

  • move container startup order and add init log messages (#1266)

v2.19.1

Choose a tag to compare

@hcloud-bot hcloud-bot released this 19 Feb 06:08
5f9b46f

Bug Fixes

  • add api client timeout (#1262)

v2.19.0

Choose a tag to compare

@hcloud-bot hcloud-bot released this 11 Feb 16:26
ef36743

Features

  • support Kubernetes v1.35 (#1245)

v2.18.3

Choose a tag to compare

@hcloud-bot hcloud-bot released this 04 Dec 14:13
24d8090

Bug Fixes

  • missing volumeattributesclasses permissions for csi-resizer (#1193)