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)

Bug Fixes

• add api client timeout (#1262)

Features

• support Kubernetes v1.35 (#1245)

Bug Fixes

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

Bug Fixes

• drop Kubernetes v1.31 support

Bug Fixes

• missing location config via node name and server id (#1158)

Features

• support Kubernetes v1.34 and drop v1.30 (#1105)

Features

• helm: add extra annotations for StorageClass (#1042)

We’ve merged our two separate binaries into a single, unified binary. This change reduces the overall container image size. Additionally, the new binary is now published as a release artifact.

The Docker image includes two compatibility scripts to support seamless image tag upgrades. However, it is still recommended to update your manifests or Helm chart to reflect the changes.

Features

• single binary (#996)
• publish binary (#1003)

In release v2.14.0, we introduced default labels that are automatically applied to every newly created volume. However, we have identified a bug in the Hetzner Cloud API that allowed invalid label keys during Volume creation. This issue affects the following labels:

1. Labels with the key prefix csi.hetzner.cloud/ are not permitted.
2. Labels using the pattern csi.storage.k8s.io/*/* are invalid due to the use of double slashes in the key.

These labels are informational only and not used by the CSI driver itself. Volumes with incorrect or broken label values will still function as expected; however, editing or updating the labels may not work correctly. To comply with API requirements, Hetzner Cloud will edit the labels for every Volume and replace them with the new labels:

• csi.hetzner.cloud/created-by - managed-by
• csi.storage.k8s.io/pvc/name - pvc-name
• csi.storage.k8s.io/pvc/namespace - pvc-namespace
• csi.storage.k8s.io/pv/name - pv-name

Features

• rename default labels on Volumes (#988)