You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,18 @@
1
1
## unreleased
2
2
3
+
## v4.0.0-beta1 - 2026.02.27
4
+
⚠️ See the [update instructions](https://github.com/cloudscale-ch/csi-cloudscale#from-csi-cloudscale-v3x-to-v4x).
5
+
6
+
**Breaking change:** This release **requires** Kubernetes VolumeSnapshot CRDs and the external snapshot controller to be installed **before** installing or upgrading this driver. Clusters without these components must install them first. Otherwise, snapshot-related operations and the snapshot resource in the Helm chart will fail to work.
7
+
8
+
* Add CSI snapshot support, including create, delete, list, and creating volumes from snapshots.
9
+
* Add `VolumeSnapshotClass` and other snapshot-related resources to the Helm chart and examples. When using Helm, snapshot classes are now created from the `csi.snapshotClasses` configuration.
10
+
* Cleaned up RBAC rules in Helm chart.
11
+
* Update `github.com/cloudscale-ch/cloudscale-go-sdk` fron `v6.0.1` to `v7.0.0`.
12
+
* Bump `google.golang.org/grpc` from `v1.77.0` to `v1.79.1`.
13
+
* Bump `github.com/sirupsen/logrus` from `v1.9.3` to `v1.9.4`.
14
+
* Bump `golang.org/x/sys` from `v0.39.0` to `v0.41.0`.
The storage classes `cloudscale-volume-ssd` and `cloudscale-volume-bulk` will be created. The
208
225
storage class `cloudscale-volume-ssd` is set to **"default"** for dynamic provisioning. If you're
209
226
using multiple storage classes you might want to remove the annotation and re-deploy it. This is
210
227
based on the [recommended mechanism](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/container-storage-interface.md#recommended-mechanism-for-deploying-csi-drivers-on-kubernetes) of deploying CSI drivers on Kubernetes
211
228
212
-
#### 3. Test and verify:
229
+
#### 4. Test and verify:
213
230
214
231
Create a PersistentVolumeClaim. This makes sure a volume is created and provisioned on your behalf:
215
232
@@ -307,6 +324,12 @@ When updating from csi-cloudscale v2.x to v3.x please note the following:
307
324
* The `region` label will stay in place for existing nodes and not be added to new nodes. It
308
325
can be safely removed from all nodes from a `csi-cloudscale` driver perspective.
309
326
327
+
### From csi-cloudscale v3.x to v4.x
328
+
329
+
Before upgrading, ensure that the Kubernetes VolumeSnapshot
330
+
CRDs and snapshot controller are installed in the cluster.
331
+
See [Required Kubernetes Snapshot Components](#1-required-kubernetes-snapshot-components).
332
+
310
333
## Advanced Configuration
311
334
312
335
Please use the following options with care.
@@ -422,15 +445,15 @@ $ git push origin
422
445
423
446
After it's merged to master, [create a new Github
424
447
release](https://github.com/cloudscale-ch/csi-cloudscale/releases/new) from
425
-
master with the version `v3.6.0` and then publish a new docker build:
448
+
master with the version `v4.0.0-beta1` and then publish a new docker build:
426
449
427
450
```
428
451
$ git checkout master
429
452
$ make publish
430
453
```
431
454
432
-
This will create a binary with version `v3.6.0` and docker image pushed to
433
-
`cloudscalech/cloudscale-csi-plugin:v3.6.0`
455
+
This will create a binary with version `v4.0.0-beta1` and docker image pushed to
0 commit comments