Merge branch 'master' into DOC-1634

docs/docs-content/clusters/cluster-management/cluster-management.md

@@ -15,9 +15,9 @@ visibility into the workloads running inside your cluster and cluster costs.
 
 The following sections describe these capabilities in detail:
 
-- [Reconfigure](reconfigure.md) - Scale your clusters up/down by adding/reducing the number of nodes in a node pool and
+- [Node Pools](node-pool.md) - Scale your clusters up/down by adding/reducing the number of nodes in a node pool and
   adding additional worker pools. Resize nodes in a node pool by modifying the node specs (CPU, Memory, or Instance Type
-  for public clouds). Add additional fault domains such as availability zones to a node pool.
+  for public clouds).
 
 - [Updates](cluster-updates.md) - Upgrade core packs (OS, Kubernetes, CSI, CNI) and add-on layers, such as Monitoring
   and Security.

docs/docs-content/clusters/cluster-management/node-pool.md

@@ -3,6 +3,7 @@ sidebar_label: "Node Pools"
 title: "Node Pools"
 description: "Learn about the node pools and applying changes to a node pool."
 hide_table_of_contents: false
+toc_max_heading_level: 2
 sidebar_position: 190
 tags: ["clusters", "cluster management"]
 ---
@@ -215,6 +216,52 @@ After you have modified a new node pool, you can validate the node pool by follo
 5. Ensure the new node pool is listed in the **Node Pools** section and that all compute instances are in the healthy
    status.
 
+## Delete a Node Pool
+
+You can delete a worker node pool from an active cluster using the following steps.
+
+:::warning
+
+The deletion of a node pool drains and removes its worker nodes. Before proceeding, ensure that your remaining node
+pools have enough resources to take on the workloads from the pool being deleted, to prevent any disruption.
+
+:::
+
+### Prerequisites
+
+- An active cluster in Palette with at least one worker node pool.
+
+- The `cluster.update` permission, which is required to edit clusters.
+
+### Delete Node Pool
+
+1. Log in to [Palette](https://console.spectrocloud.com).
+
+2. From the left **Main Menu**, click **Clusters**.
+
+3. Select the cluster with the node pool you want to delete.
+
+4. Click the **Nodes** tab.
+
+5. Locate the node pool you want to delete and click the **Delete** button.
+
+6. Click **Delete** again to confirm the deletion. This action will drain and delete all nodes in the node pool.
+
+### Validate
+
+Use the following steps to confirm that the node pool was deleted successfully.
+
+1. Log in to [Palette](https://console.spectrocloud.com).
+
+2. From the left **Main Menu**, click on **Clusters**.
+
+3. Select the cluster that had the deleted node pool.
+
+4. Click the **Nodes** tab.
+
+5. Verify that the deleted node pool is no longer listed in the **Node Pools** section and that all the remaining
+   compute instances are in a healthy state.
+
 ## Approve Cluster Repave
 
 ### Prerequisites

docs/docs-content/clusters/edge/edge-configuration/installer-reference.md

@@ -128,7 +128,7 @@ stylus:
 #### Registry Mapping Rules
 
 Use registry mapping rules to map a domain name to an external registry. The `registryMappingRules` parameter accepts a
-list of key-value pairs where the key is the domain name and the value is URL mapping to the external registry.
+list of key-value pairs where the key is the domain name and the value is a URL mapping to the external registry.
 
 Below is an example of registry mapping rules. The registry in the code snippet, `example.registry.com/internal-images`
 is assumed to contain the images that are mapped from the external registries.
@@ -148,6 +148,13 @@ stylus:
       "grc.io/spectro-images-public": "example.registry.com/internal-images"
 ```
 
+All matched portion on the source URL will be replaced with the mapped value and any unmatched path is preserved. Using
+the example in the following diagram, if an image named `alpine:latest` is stored at
+`somedomain.com/somepath/example-repo/alpine:latest`, the mapping rules will rewrite image pulls so that they reference
+`targetdomain.com/other/path/example-repo/alpine:latest`.
+
+![Example of registry mapping rules](/clusters_edge_edge-configuration_installer-reference_registry-mapping.webp)
+
 ##### Airgap Environment
 
 In an airgap environment, use the `registryMappingRules` parameter to map domain names to external registries that were

redirects.js

@@ -594,6 +594,10 @@ let redirects = [
     from: "/clusters/cluster-management/noc-ui/",
     to: "/clusters/cluster-management/cluster-map-filters/",
   },
+  {
+    from: "/clusters/cluster-management/reconfigure/",
+    to: "/clusters/cluster-management/node-pool/",
+  },
   {
     from: [
       "/integrations/antrea-cni",