aws-efs-csi-driver release v4.0.0

  • crossaccount is no longer accepted in mountOptions. Driver v3.x rejects it with InvalidArgument in both CreateVolume and NodePublishVolume.
  • updateStrategy was replaced by rollingUpdate. controller.updateStrategy and node.updateStrategy no longer exist. Use controller.rollingUpdate and node.rollingUpdate, which accept only the RollingUpdate parameters (maxSurge, maxUnavailable), so you can no longer set’ OnDelete’ for the node DaemonSet. We don’t set either key, so the defaults don’t change. The values schema allows unknown keys, so a leftover updateStrategy override in the App CR config is ignored without error. Move it to rollingUpdate.

Changed

  • Update OCIRepository version to v1.
  • Update upstream aws-efs-csi-driver chart to 4.5.0 (was 3.4.1), which moves the driver image from v2.3.1 to v3.5.0 and refreshes the csi-node-driver-registrar and livenessprobe sidecars. Upstream chart declares kubeVersion: >=1.17.0-0, covering Kubernetes 1.35.
  • Correct the stale io.giantswarm.application.upstream-chart-version annotation, which still claimed 2.3.0.
  • Bundle: bump the pinned image tags in lockstep with the chart, since the bundle forwards them to the app chart under upstream: and would otherwise run the new templates against the old driver: aws-efs-csi-driver v2.3.0 -> v3.5.0, livenessprobe v2.17.0 -> v2.19.0, csi-node-driver-registrar v2.15.0 -> v2.17.0, csi-provisioner v6.1.0 -> v6.3.0.