feat(block-storage): add macro for information for k8s users (#4199)

Author: nerda-codes

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

@@ -23,6 +23,8 @@ During migration, unified snapshots will be converted into [Block Storage Low La
 
 This guide offers step-by-step instructions to migrate your volumes and snapshots using either the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool (recommended) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-volumes-migrate-a-volume-andor-snapshots-to-sbs-scaleway-block-storage).
 
+<Macro id="block-storage-no-migration-for-k8s" />
+
 <Message type="note">
   - The easiest way to migrate your Block Storage volumes and snapshots is by using the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool
   - If you encounter an error about quota limitations during the migration process, [contact our support team](https://console.scaleway.com/support/tickets/create) for assistance.

macros/storage/block-storage-no-migration-for-k8s.mdx

@@ -0,0 +1,8 @@
+---
+macro: block-storage-no-migration-for-k8s
+---
+
+<Message type="important">
+ <br></br>
+  **Kubernetes customers must not migrate their block volumes to the Block Storage API to prevent major disruptions to their Kubernetes service and block volume unavailability.** You can identify your volumes by [listing them](/storage/block/api-cli/identifying-volume-snapshot-api/#listing-volumes-created-with-the-block-storage-api) and referring to the `name` field, next to which you should see an output similar to `k8s_base_node_2024-07-26`.
+</Message>

storage/block/reference-content/advantages-migrating-to-sbs.mdx

@@ -15,9 +15,7 @@ categories:
 
 This page explains why **Instance users** should migrate from the Instance API to the Block Storage API to create and manage block volumes and snapshots.
 
-<Message type="important">
-  The information displayed on this page **does not apply to Kapsule users with persistent block volumes**. You can identify them by [listing your volumes](/storage/block/api-cli/identifying-volume-snapshot-api/#listing-volumes-created-with-the-block-storage-api) and referring to the `name` field, next to which you should see an output similar to `k8s_base_node_2024-07-26`.
-</Message>
+<Macro id="block-storage-no-migration-for-k8s" />
 
 ## Transitioning from the Instance API to the Block Storage API for volume and snapshot management