Releases: kubernetes-sigs/ibm-vpc-block-csi-driver
v5.2.9
CHANGELOG
- New Features
- Added support for the cross account snapshot restore.
- Updated below CSI sidecar versions
- csi-provisioner:v5.0.2
- csi-attacher:v4.6.1
- csi-resizer:v1.11.2
- csi-snapshotter:v8.0.1
- livenessprobe:v2.13.1
- csi-node-driver-registrar:v2.11.1
- Updated golang version to 1.22
- Updated to k8s 1.30 client libraries
- Update CSI Spec Version to 1.9.0
- CSI sidecar livenessprobe will run as non-root user/group in Node Server pod.
Urgent Upgrade Notes
No, really, you MUST read this before you upgrade:
Previous releases are not compatible with updated deployment files associated with the current release due to the changes in csi sidecar livenessprobe securityContext changes.
https://github.com/kubernetes-sigs/ibm-vpc-block-csi-driver/blob/master/deploy/kubernetes/driver/kubernetes/manifests/node-server.yaml
E.g. If using manifests from old release lets say v5.2.8 and wants to use the latest code, it is recommended to use the latest manifests
v5.1.13
CHANGELOG
- Updated below CSI sidecar versions
- csi-provisioner:v5.0.2
- csi-attacher:v4.6.1
- csi-resizer:v1.11.2
- csi-snapshotter:v8.0.1
- livenessprobe:v2.13.1
- csi-node-driver-registrar:v2.11.1
- Updated golang version to 1.22
- Updated to k8s 1.30 client libraries
- Update CSI Spec Version to 1.9.0
- CSI sidecar livenessprobe will run as non-root user/group in Node Server pod.
No, really, you MUST read this before you upgrade:
Previous releases are not compatible with updated deployment files associated with the current release due to the changes in csi sidecar livenessprobe securityContext changes.
Eg. If using manifests from old release lets say v5.1.12, and wants to use the latest code, it is recommended to use the latest manifests
v5.1.12
Upgrade to google.golang.org/protobuf@v1.33.0 and github.com/golang/protobuf@v1.5.4 to address CVE-2024-24786.
v5.2.8
v5.1.11
Update in golang.org/x/net package to 0.19.0 due to CVE - CVE-2023-39325 https://www.mend.io/vulnerability-database/CVE-2023-39325.
