Aks node pools doc 2103 (#5101)

* Update dense-mode-and-node-pools.md

* Update dense-mode-and-node-pools.md

* Update dense-mode-and-node-pools.md

* Update dense-mode-and-node-pools.md

* Update dense-mode-and-node-pools.md

* Update dense-mode-and-node-pools.md

* Update dense-mode-and-node-pools.md

* Update dense-mode-and-node-pools.md

* Update dense-mode-and-node-pools.md

src/docs/ocean/features/dense-mode-and-node-pools.md

@@ -33,3 +33,58 @@ Ocean switches to dense mode when one of these conditions is met:
 * The Azure AKS version is not supported: Ocean switches to dense mode when the cluster cannot create new node pools (Azure AKS Limitation) and can only scale existing ones because Azure no longer supports the AKS version used by the cluster.
 
 In dense mode, Ocean only uses existing node pools for scaling operations and does not create new ones.
+
+## View Node Pools in the Console
+
+To access the Node pools tab:
+* Click **Ocean > Cloud Clusters** on the left main menu.
+* Select a cluster from the list of clusters.
+* Click the **Node Pools** tab.
+
+<details style="background:#f2f2f2; padding:6px; margin:10px 0px 0px 0px">
+   <summary markdown="span" style="color:#7632FE; font-weight:600">Click to view image</summary>
+
+   <div style="padding-left:16px">
+
+   <img width="1200" src="https://github.com/user-attachments/assets/78c534a7-8581-4cbb-a410-1a8be3b75dab" />
+
+</div>
+
+</details>
+
+The node pools list contains these columns:
+
+* Node Pool: Click on the link to open the node pool details, attributes, and list of nodes (in the Nodes tab).
+  * You can sort this column by either name or [status](https://docs.spot.io/ocean/features/dense-mode-and-node-pools?id=node-pool-status).
+* Virtual Node Group: Click on the link to open the configuration for the virtual node group.
+* Availability Zone: Availability zone for the node pool.
+* VM Size: Machine type.
+* Life Cycle: Regular or spot.
+* Node Count: Number of nodes in the node pool.
+* OS: For example, Linux.
+* OS Disk: Ephemeral or managed.
+* OS SKU: For example, Ubuntu.
+* Image: Image name.
+* K8s version: Kubernetes version number.
+
+### Node Pool Status
+
+* ![icon-successful-20](https://github.com/user-attachments/assets/699bf863-e329-4260-965d-3119809a0755) Running successfully.
+* ![icon-spinner](https://github.com/user-attachments/assets/eec9cbca-90d5-43cc-bef6-801ac4caa746) Spinner (node pool being processed).
+* ![icon-lock](https://github.com/user-attachments/assets/4d48eece-0127-4c82-b108-5a5e5530a34f) Locked. When a node pool is locked in Azure, modifications, scaling, or deletions by Ocean are restricted to ensure stability and prevent unintended changes. The locking mechanism helps maintain operational integrity during critical operations.
+* ![icon-warmedup](https://github.com/user-attachments/assets/6ade61d6-3bca-44c3-b644-21c5597ae12f) Warmed-up: Node pool that has been pre-provisioned and is ready to manage workloads:
+  * Pre-provisioning: Nodes in a warmed-up pool are created in advance, which reduces the time needed to scale up when traffic increases. This helps ensure that applications can respond quickly to sudden spikes in demand.
+  * The nodes are ready, meaning they are fully initialized and can accept pods without the delay associated with starting new nodes from scratch.
+  * Use case: This is particularly useful for applications with predictable traffic patterns, improving performance and reliability.
+*  ![icon-unmanaged1](https://github.com/user-attachments/assets/ec73f5a1-0f69-49ca-87e8-6ecd450da37c)  Unmanaged Node Pool.
+
+
+
+
+
+
+
+
+
+
+