update sidecar containers

[disperate]

To pass the integration tests I had to align the mismatched topology keys in NodeGetInfo and CreateVolume to "csi.cloudscale.ch/zone".

[alakae]

Thanks!

From my understanding, the fix you implemented is necessary if persistentvolume.spec.nodeAffinity is set. This happens when csi-provisioner topology support is turned on. To clarify why this was not an issue with the earlier versions of sig-storage/csi-provisioner:

• v3.2.1: had no Topology support
• v4.0.0: dito
• v5.0.0: introduced the Feature Gate (enabled by default)
• v6.0.0: dito
• v6.1.0: dito

Interestingly, the announced removal of the feature gate in v5.0.0 still has not oc ecurred.

My suggestion is: toggle the feature gate to off, which essentially brings back the old behavior and implement popper Topology support in a dedicated issue (side note: we can probably remove this check at that point:

csi-cloudscale/driver/controller.go

Line 88 in fa03b5c

if req.AccessibilityRequirements != nil {

). Technically, it would not even require your fix in this case, but we should keep it anyways.

In conclusion, it is deemed safe for users to apply this upgrade to their clusters, provided they did not change anything related to how Topology is handled in their cluster.

Additionally: v6.1.0 of external-provisioner officially requires Kubernetes 1.34. Although our test suite also passes with 1.33. Similar problem with v2.0.0 of sig-storage/csi-resizer.

Let's discuss if we want to stick to older versions of these side-cars for now.