Skip to content

chore(kapsule): remove part on SBS CSI migration #5521

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 16, 2025
Merged

chore(kapsule): remove part on SBS CSI migration #5521

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
57 changes: 1 addition & 56 deletions pages/kubernetes/api-cli/managing-storage.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,65 +31,10 @@ To verify if the driver is running, use the following command:
kubectl get csidriver
```

The output of this command provides a quick status update on the CSI plugin within your Kubernetes cluster. For the latest features and enhancements, consider upgrading to [release 0.3](https://github.com/scaleway/scaleway-csi/tree/release-0.3#block-storage-low-latency), which supports **[Block Storage low latency](/block-storage/quickstart/)** volumes.
The output of this command provides a quick status update on the CSI plugin within your Kubernetes cluster.

To identify your current CSI release version, navigate to the [Cockpit interface](/cockpit/how-to/access-grafana-and-managed-dashboards/), specifically the **Kubernetes Cluster - Overview** dashboard.

## Upgrading to CSI version 0.3

<Message type="important">
The Scaleway Block Volume Container Storage Interface (CSI) driver **v0.2** will reach its end of support on **February 28, 2025**.
</Message>

The migration moves volumes from the [Instances API](https://www.scaleway.com/en/developers/api/instance/) to the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/). No volume detachment is expected, only a control plane restart.
Newer storage classes have been introduced, with `sbs-default` set as the new default. The existing `scw-bssd` and `scw-bssd-retain` storage classes will remain available for now.


### Using the API with curl

You can trigger the migration to SBS-CSI using the following `curl` command:

```bash
curl "https://api.scaleway.com/k8s/v1/regions/$REGION/clusters/$CLUSTER_ID/migrate-to-sbs-csi" \
-X POST \
-H "X-Auth-Token: $TOKEN"
```

Replace the placeholders with the following:

- `$REGION`: Your cluster's region (e.g., `fr-par`, `nl-ams`).
- `$CLUSTER_ID`: Your cluster ID.
- `$TOKEN`: Your Scaleway API token.

This command will initiate the migration process for your cluster to the new SBS-CSI.

### Using the Scaleway CLI

Alternatively, you can use the Scaleway CLI to perform the migration. Ensure the CLI is installed and configured with your API credentials.

1. Install and configure the Scaleway CLI, if you have not already:
```bash
scw init
```

2. Run the migration command:

```bash
scw k8s cluster migrate-to-sbs-csi $CLUSTER_ID region=$REGION
```

Replace `$REGION` and `$CLUSTER_ID` with your cluster’s region and ID, respectively.

### Post-migration verification

After initiating the migration, the cluster status will change to _updating_. Once the migration completes, you can verify that the CSI driver has been updated and that the new driver properly handles Persistent Volume Claims (PVCs).

```bash
kubectl get csidriver
```

This command will confirm that the migration was successful.

## Going further

* [Creating persistent volumes with Scaleway Block Storage](https://github.com/scaleway/scaleway-csi/tree/release-0.3/examples/kubernetes#pvc--deployment)
Expand Down