docs(ins): add warning for kapsule nodes

menu/navigation.json

@@ -1875,6 +1875,14 @@
                     "label": "Connect to a cluster with kubectl",
                     "slug": "connect-cluster-kubectl"
                   },
+                  {
+                    "label": "Create a new node Kapsule node pool",
+                    "slug": "create-node-pool"
+                  },
+                  {
+                    "label": "Migrate a Kapsule node pool",
+                    "slug": "migrate-node-pool"
+                  },
                   {
                     "label": "Deploy an image from Container Registry",
                     "slug": "deploy-image-from-container-registry"

pages/instances/api-cli/migrating-instances.mdx

@@ -26,6 +26,10 @@ To do so, you need the Instance’s ID and a valid API key.
   Network interface names may vary across commercial families (e.g. ENT1 vs. POP2). Ensure that any hardcoded interface names in your configurations or scripts are updated to avoid migration issues.
 </Message>
 
+<Message type="important">
+  Do **not** manually change the commercial type of **Kubernetes Kapsule nodes** using the API or CLI. Kubernetes Kapsule nodes **must be managed** through Kubernetes. Modifying node types outside of the recommended method can lead to instability or unexpected behavior.
+  To change the commercial type of your nodes, create a new node pool with the desired Instance type and [migrate your workloads](/kubernets/how-to/migrate-node-pool/) to the new pool.
+</Message>
 <Tabs id="updateinstance">
   <TabsTab label="CLI">
 

pages/kubernetes/how-to/create-node-pool.mdx

@@ -0,0 +1,36 @@
+---
+meta:
+  title: Create a new Kubernetes Kapsule node pool
+  description: Learn how to add a new node pool to an existing Kubernetes Kapsule cluster.
+content:
+  h1: Create a new Kubernetes Kapsule node pool
+  paragraph: Learn how to add a new node pool to an existing Kubernetes Kapsule cluster.
+tags: kubernetes kapsule kosmos
+dates:
+  validation: 2025-06-23
+  posted: 2025-06-23
+categories:
+  - containers
+---
+
+This documentation provides step-by-step instructions on how to create a new node pool for an existing Kubernetes Kapsule cluster.
+
+<Macro id="requirements" />
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/)
+
+1. Navigate to **Kubernetes** under the **Containers** section of the [Scaleway console](https://console.scaleway.com/) side menu. The Kubernetes dashboard displays.
+2. Click the Kapsule cluster name you want to manage. The cluster information page displays.
+3. Click the **Pools** tab to display the pool configuration of the cluster.
+4. Click **Add pool** to launch the pool creation wizard.
+5. Configure the pool:
+    - Choose the **Availability Zone** for the pool.
+    - Choose the commercial type of Instance for the pool.
+    - Configure the system volume.
+    - Configure pool options.
+    - Enter the pool's details.
+6. Click **Add pool**. The pool gets added to your basket. Repeat the steps above to configure addional pools.
+7. Click **Review** once you have configured the desired pools. A summary of your configuration displays.
+8. Verify your configuration and click **Submit** to add the pool(s) to your Kapsule cluster.

pages/kubernetes/how-to/migrate-node-pool.mdx

@@ -0,0 +1,47 @@
+---
+meta:
+  title: Migrating Kubetnetes workloads to a new node pool
+  description: Learn how to migrate existing Kubernetes workloads to a new node pool.
+content:
+  h1: Migrating Kubetnetes workloads to a new node pools
+  paragraph: Learn how to migrate existing Kubernetes workloads to a new node pool.
+tags: kubernetes kapsule kosmos
+dates:
+  validation: 2025-06-23
+  posted: 2025-06-23
+categories:
+  - containers
+---
+
+This documentation provides step-by-step instructions on how to migrate Kubernetes workloads from one node pool to another within a Kubernetes Kapsule cluster.
+Migrating workloads can be required to change the commercial type of Instance for your pool, or to scale your infrastructure.
+
+<Macro id="requirements" />
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/)
+- Have an existing node pool that you want to migrate
+
+<Message type="important">
+  Always ensure that your **data is backed up** before performing any operations that could affect it.
+</Message>
+
+1. Create the new node pool with the desired configuration either [from the console](/kubernetes/how-to/create-node-pool/) or by using `kubectl`.
+    <Message type="tip">
+      Ensure that the new node pool is properly labeled if necessary.
+    </Message>
+
+2. Run `kubectl get nodes` to check that the new nodes are in a `Ready` state.
+
+3. Cordon the nodes in the old node pool to prevent new pods from being scheduled there. For each node, run: `kubectl cordon <node-name>`
+
+4. Drain the nodes to evict the pods gracefully.
+   - For each node, run: `kubectl drain <node-name> --ignore-daemonsets --delete-emptydir-data`
+   - The `--ignore-daemonsets` flag is used because daemon sets manage pods across all nodes and will automatically reschedule them.
+   - The `--delete-emptydir-data` flag is necessary if your pods use emptyDir volumes, but use this option carefully as it will delete the data stored in these volumes.
+   - Refer to the [official Kubernetes documentation](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) for furher information.
+
+5. After draining, verify that the pods have been rescheduled to the new node pool. Run `kubectl get pods -o wide` after daraining, to verify that the pods have been rescheduled to the new node pool
+
+6. Delete the old node pool once you confirm that all workloads are running smoothly on the new node pool,