Aks wkload mig imps doc 2019 (#5308)

* Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md * Update migrate-workload-aks-ui.md
spotinst · Jan 14, 2025 · fb08a6c · fb08a6c
1 parent 2bfff61
commit fb08a6c
Showing 1 changed file with 83 additions and 37 deletions.
diff --git a/src/docs/ocean/tutorials/migrate-workload-aks-ui.md b/src/docs/ocean/tutorials/migrate-workload-aks-ui.md
@@ -1,47 +1,92 @@
 #  Migrate AKS Workload using the Console
 
-This topic describes migrating your existing Kubernetes K8s workloads into an Ocean cluster via the Ocean Console.
+This topic describes migrating your existing Kubernetes workloads into an Ocean cluster via the Ocean console.
 
 Before starting, review the [prerequisites](https://docs.spot.io/ocean/tutorials/migrate-workload-aks?id=prerequisites).
 
 ##  Step 1: Select Instances to Migrate
 
 1.  In the left main menu, click **Ocean** and click **Cloud Clusters**. 
 2.  Select a cluster from the list of clusters.
-3.  Click **Start Migration** on the left of the screen under Ocean Managed Nodes. 
+3.  Click **Start Migration** on the right under Ocean Managed Nodes. 
 
-![migration-nodes-managed](https://github.com/user-attachments/assets/a669c8d3-3c94-4ec8-bd97-993261428abc)
+<img width="500" src ="https://github.com/user-attachments/assets/b53d540e-424c-4e9b-b196-d0aab6550496" />
 
 >**Note**: Worker nodes are the main compute resources running containerized applications in a Kubernetes cluster. System nodes (or master nodes) are the control plane components that manage the overall Kubernetes cluster and the workloads running on the worker nodes. The regular nodes are the on-demand nodes. The recommendation is to migrate the unmanaged worker nodes to become Ocean-managed Nodes. In the example above, before migration, there are no Ocean-managed nodes.
 
-Once you start migration, Ocean automatically detects the workloads (nodes and pods) of the associated Kubernetes cluster and displays a list of all the discovered nodes.
+Once you start the migration, Ocean automatically detects the workloads (nodes and pods) of the associated Kubernetes cluster and displays a list of all the discovered nodes.
 
-![aks-ready-for-migration](https://github.com/user-attachments/assets/962c3046-fc0a-42ca-8675-dad2d46c6e9c)
+<img width="900" src ="https://github.com/user-attachments/assets/b447a35b-26fd-4c2c-90e1-10cfce264d2b" />
 
-4.  Select the nodes (instances) you want to migrate into your Ocean cluster.
-    * If any node entries display the **Required Validation** status in the **Ready for Migration** column, click **Validate** at the bottom left of the screen. When the validation process is completed, if any node entries display the **Unable to migrate** status in the **Ready for Migration** column, click the down arrow on the left to drill down to the workloads.
+The list of discovered nodes contains these columns:
 
-![aks-migration-validations](https://github.com/user-attachments/assets/c0e4f51f-2de8-4dce-8670-3f8a824641b6)
+* Migration Node: Node for migration.
+* Node Group.
+* Pod Count: Number of pods on node.
+* Virtual Node Group Match: Indicates whether an existing virtual node group in the cluster matches the node.
+* Ready for Migration (Node Statuses):
+   * <img width="20" src ="https://github.com/user-attachments/assets/41b067f4-9df4-41cd-9aac-0289409a9a73 " /> Ready for migration: Node is validated and can be migrated (green color).
+   * <img width="20" src="https://github.com/user-attachments/assets/fbb5322b-7b34-4f41-8883-49a88f10958d" /> Excluded: Node was not selected for migration (gray color).
+   * <img width="20" src ="https://github.com/user-attachments/assets/1be4c530-7c3c-44b9-8564-f0128c4803c5 " /> Unable to migrate: Node cannot be migrated (red color).
+   * <img width="20" src ="https://github.com/user-attachments/assets/d21899f7-d922-4f36-a2bf-835b8831f112" /> Requires validation: Nodes are checked before migration to ensure successful migration. If an issue is identified for a node, you can either fix it or select a different node. 
 
-Nodes are checked before migration to ensure successful migration. If an issue is identified for a node, you can either fix it or select a different node. 
-Validation checks for the following:
-*  Virtual Node Group Match: At least one Virtual Node Group in the cluster must match the specific node.
+Node validation checks for the following:
+*  Virtual Node Group Match: At least one virtual node group in the cluster must match the specific node.
 *  Support for the Kubernetes version.
 *  Support for the Ocean Controller version.
 *  Whether Spot toleration exists.
 *  Specific Constraints: For example, Restrict Scale Down, Respect Pod Disruption Budget (PDB), PVC.
 
-Node Statuses:
+4. Select the nodes (instances) you want to migrate into your Ocean cluster.
+5. If any selected node entries display the **Required Validation** status in the **Ready for Migration** column, click **Validate** at the bottom left of the screen.
+6. When the validation process is completed, check if any node entries display the **Unable to migrate** status in the **Ready for Migration** column.
+
+<img width="900" src ="https://github.com/user-attachments/assets/9d896950-383c-4648-832c-2646dbc40574" />
+
+7. Fix any required nodes Ocean cannot migrate (see below) before you Click **Next**.
+
+<details style="background:#f2f2f2; padding:20px; margin:10px 0px 0px 0px">
+
+  <summary markdown="span" style="color:#7632FE; font-weight:600">What to do about nodes that Ocean cannot migrate (click for more info...)
+</summary>
+
+<div style="padding-left:16px">
+
+If the virtual node group match column displays **No match** and has a **click to edit** link, the node does not contain labels and taints attributes that match any configured virtual node group in the cluster. 
+
+To edit:
+
+1. Click the link. An issues dialog box displays the labels and taints required for a virtual node group in your cluster to match the selected node.
+
+   <img width="650" src ="https://github.com/user-attachments/assets/08b4b68f-13d3-4de7-8a07-76993b480740" />
+
+2. Click **Create New VNG** to create a virtual node group that contains these injected attributes. See how to configure a [virtual node group](https://docs.spot.io/ocean/tutorials/manage-virtual-nd-groups-aks?id=createedit-a-virtual-node-group) in the edit screen.
+
+   <img width="650" src ="https://github.com/user-attachments/assets/5b693b5d-cdbc-4ab1-8d43-27dc98779727" />
+
+>**Note**: The new virtual node group's other attributes are inherited from the virtual node group template.
+  
+If the virtual node group Match column shows **No match** (but there is no link), the tooltip shows the reason for the mismatch. Spot recommends checking your Azure workloads related to the Ocean virtual node group configuration to ensure they are correct and resolve any mismatches.
+
+If you drill down to a workload under a node and the <img width="20" src ="https://github.com/user-attachments/assets/2c5d0898-d226-4867-a6d2-acde7ca2fee7" /> **Spot toleration is missing** message appears, [Install the admission mutating webhook](https://docs.spot.io/ocean/getting-started/aks/?id=step-4-automatic-spot-tolerance-injection-optional)  that injects the required spot toleration, which AKS requires to run pods on spot nodes:
+* To do this, click **Actions > Spot Toleration Injection** (top-right of screen).
+
+
+
+>**IMPORTANT:** If no nodes pass the validation process, you must fix errors before migrating.
+
+You can migrate if at least 1 of the selected nodes is successfully validated.
+
+ </div>
+
+</details>
 
-*   Ready for migration: Node is validated and can be migrated (green color)
-*   Excluded: Node was not selected for migration (gray color).
-*   Unable to migrate: Node cannot be migrated (red color)
 
 ##  Step 2: Set Preferences
 
 Select your workload migration preferences.
 
-![migration-nodes-prefs](https://github.com/user-attachments/assets/dfd21e4b-15da-404e-a81d-6b34d103c421)
+![migration-preferences](https://github.com/user-attachments/assets/ac7d2007-f4ff-4572-a15b-8d56a0aaf85e)
 
 *  **Batch Size Percentage**: Indicates the percentage of the cluster's target capacity that will be migrated during migration (per batch). For example, if the cluster's target capacity is 50 nodes, and the Batch Size Percentage is set to 20%, each batch will consist of 20% of the target capacity, 10 nodes (50 nodes * 20% = 10 nodes).   
 *  **Batch Size Healthy Percentage**: indicates the minimum percentage of (migrated) healthy nodes in a single batch.
@@ -52,7 +97,7 @@ The migration will fail if the number of healthy nodes in a single batch is belo
 *  **Respect Restrict Scale Down during Roll**: Rolls do not consider the restrict-scale-down label. Ocean will migrate a node even if a task or pod uses this label. Ocean's Autoscaler considers all configured constraints before the roll.
 *  **Delete node from Azure after successful migration**: Select to delete the node from the Azure console because Ocean now manages the node.
 
->**Note**: Before migration, the Azure-managed node pools are changed from automatic to manual scaling to avoid race conditions.
+>**Note**: Before migration, the Azure-managed node pools are changed from automatic to manual scaling to avoid conflicts.
 
 
 ##  Step 3: Start Migration
@@ -63,42 +108,43 @@ The migration will fail if the number of healthy nodes in a single batch is belo
 
 Follow the migration in the dashboard.
 
-<img width="1224" alt="Migration Process" src="https://github.com/spotinst/help/assets/159915991/1fc07669-40d4-4505-8765-1756fc46b79f">
+<img width="900" alt="Migration in Process" src="https://github.com/user-attachments/assets/918ea141-bb49-4853-910f-4cd21d744f70" />
 
 Node Statuses:
 
-*  In Progress: Migration has started (dark blue color)
-*  Migrated: Node has been migrated (green color)
-*  Not Migrated: Node was not migrated due to stopped migration (gray color).
-*  To be Migrated: Node has not yet been migrated (light blue color)
-*  Failed: Migration failed (red color)
-*  Manually Excluded: Node was not selected for migration (gray color)
+*  <img width="20" src ="https://github.com/user-attachments/assets/ed362ecb-bfb5-4d85-aada-8941e96a94a7" /> In Progress: Migration has started (dark blue color)
+*  <img width="20" src ="https://github.com/user-attachments/assets/41b067f4-9df4-41cd-9aac-0289409a9a73 " /> Migrated: Node has been migrated (green color).
+*  <img width="20" src="https://github.com/user-attachments/assets/fbb5322b-7b34-4f41-8883-49a88f10958d" /> Not Migrated: Node was not migrated due to stopped migration, or was manually excluded for migration (gray color).
+*  <img width="20" src ="https://github.com/user-attachments/assets/1d4e0b3d-de64-490b-a408-e823d3d24a1e" /> To be Migrated: Node has not yet been migrated (light blue color)
+*  <img width="20" src ="https://github.com/user-attachments/assets/1be4c530-7c3c-44b9-8564-f0128c4803c5 " /> Failed: Migration failed (red color)
 
 ###  Stop Migration
 
 You can stop a migration in progress. However, migrated workloads remain under the new Spot nodes. Spot completes scheduling all the unscheduled pods of the current batch, and undrained nodes become schedulable again.
 
-To stop the migration process in progress.
+To stop the migration:
 
-1.  Click **Stop Migration**.
-2.  Select **Terminate Drained Instances** if you want Ocean to terminate the already drained nodes before stopping the entire process.
+1.  Click **Stop Migration** on the right of the screen (above the nodes list).
+2.  Click **Terminate Drained Instances** if you want Ocean to terminate the already drained nodes before stopping the entire process.
 
 ##  View Previous Migrations
 
-To view previous migrations:
-
-1.   From the Actions drop-down menu at the top-right of the screen, click **Previous Workload Migrations**.
+To view previous migrations (for the past month):
 
-![workloads-previous-migrations2](https://github.com/user-attachments/assets/a2f1d1a8-afbb-40d9-bf90-9170421188fc)
+* Click **Actions > Previous migration history** on the top-right of the screen, or click **Migrations History** (from the workload migration dashboard).
 
-2.  Click on the required entry under Migrated Nodes to display the dashboard for that migration.
+  <img width="650" src ="https://github.com/user-attachments/assets/292306b9-ffb1-49fb-9d51-a242d93a98c1" />
 
-    Previous Migration Statuses:
+The list of migrations displays:
 
-    *  Finished: All nodes were migrated.
-    *  Partly Completed: At least one selected node was not migrated.
-    *  Stopped: Migration was manually stopped.
-    *  Failed: Migration failed.
+* Migration ID.
+* Start Date of migration.
+* Number of migrated nodes (x/y). Click the link to display the dashboard for that migration.
+* Status of the migration.
+   *  <img width="20" src ="https://github.com/user-attachments/assets/41b067f4-9df4-41cd-9aac-0289409a9a73 " /> Completed: All nodes were migrated.
+   *  <img width="20" src ="https://github.com/user-attachments/assets/ed362ecb-bfb5-4d85-aada-8941e96a94a7" /> Partly migrated (in progress): At least one selected node was not migrated.
+   *  <img width="20" src="https://github.com/user-attachments/assets/fbb5322b-7b34-4f41-8883-49a88f10958d" /> Stopped: Migration was manually stopped.
+   *  <img width="20" src ="https://github.com/user-attachments/assets/1be4c530-7c3c-44b9-8564-f0128c4803c5 " /> Failed: Migration failed.