Skip to content

Commit 0c0d66c

Browse files
fix(k8s): add warning (#4327)
* fix(k8s): add warning * Apply suggestions from code review * Update migrate-volumes-snapshots-to-sbs.mdx * Update pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --------- Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com>
1 parent 730504d commit 0c0d66c

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,9 @@ This guide offers step-by-step instructions to migrate your volumes and snapshot
3838
Alternatively, you can use the [snapshot export/import feature](/instances/api-cli/snapshot-import-export-feature/) to migrate your unified volumes and snapshots to Block Storage Low Latency volumes.
3939

4040

41-
<Macro id="block-storage-no-migration-for-k8s" />
41+
<Message type="important">
42+
Volumes **created and managed through Kubernetes** do not fall within the scope of the migration described on this page. Find specific instructions for migrating Kubernetes volumes behind the Scaleway Block Storage API in the [managing storage for Kubernetes documentation](/kubernetes/api-cli/managing-storage/#upgrading-to-csi-version-03).
43+
</Message>
4244

4345
<Macro id="requirements" />
4446

0 commit comments

Comments
 (0)