feat(k8s): update doc

Author: bene2k1

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

@@ -31,17 +31,12 @@ Migrating workloads can be required to change the commercial type of Instance fo
     <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 further information.
-
 5. Run `kubectl get pods -o wide` after draining, to verify that the pods have been rescheduled to the new node pool.
-
 6. [Delete the old node pool](/kubernetes/how-to/delete-node-pool/) once you confirm that all workloads are running smoothly on the new node pool.