spectrocloud · achuribooks · Aug 17, 2025 · Jul 28, 2025 · Jul 28, 2025 · Jul 30, 2025
@@ -0,0 +1,16 @@
+---
+partial_category: self-hosted
+partial_name: upgrade-palette-prereqs
+---
+
+- A healthy {props.version} management cluster where you can access the Local UI of the leader node.
+
+  - Verify that your local machine can access the Local UI, as airgapped environments may have strict network policies preventing direct access.
+
+- If using an external registry, ensure your local machine has access to the external registry server and you have the necessary permissions to push images to the registry.
+
+  - (Optional) The Palette CLI installed on your local machine if you would like to use it to upload content to your external registry. Refer to the <VersionedLink text="Palette CLI" url="/automation/palette-cli"/> guide for installation instructions.
+
+- Access to the [Artifact Studio](https://artifact-studio.spectrocloud.com/) to download the content bundle for {props.version}.
+
+  - Check that your upgrade path is supported by referring to the <PaletteVertexUrlMapper edition={props.edition} text="Supported Upgrade Paths" url="/upgrade#supported-upgrade-paths"/>.
@@ -0,0 +1,16 @@
+---
+partial_category: self-hosted
+partial_name: upgrade-palette-validate
+---
+
+1. Log in to the Local UI of the leader host of the {props.version} management cluster. By default, Local UI is accessible at `https://<node-ip>:5080`. Replace `<node-ip>` with the IP address of the leader host.
+
+2. From the left main menu, click **Cluster**.
+
+3. Check that the `palette-mgmt-plane` pack displays the upgraded version number and is in a **Running** status.
+
+4. Verify that you can log in to the {props.version} system console and no warning message is displayed.
+
+5. If you have configured a tenant, log in to the tenant console and verify that Palette displays the correct version number.
+
+   ![Palette version in tenant console](/enterprise-version_install-palette_palette-management-appliance_palette-tenant-version.webp)
@@ -7,7 +7,7 @@ partial_name: upload-packs-enablement
 
 <TabItem value="internal-zot-registry" label="Internal Zot Registry">
 
-<Tabs>
+<Tabs groupId="upload-method">
 
 <TabItem label="Local UI Method" value="local-ui-method">
 
@@ -34,7 +34,7 @@ partial_name: upload-packs-enablement
    The upload process starts automatically once the files are selected. You can monitor the upload progress in
    the **Upload Content** dialog.
 
-   Wait for the **Upload Successful** confirmation message to appear.
+   Wait for the **File(s) uploaded successfully** confirmation message or the green check mark to appear next to the upload progress bar.
 
 8. Log in to the {props.version} system console.
 
@@ -69,9 +69,9 @@ partial_name: upload-packs-enablement
 
 6. Upload the pack bundles to the internal Zot registry using the Palette CLI. Replace `<pack-zst>` with your downloaded pack bundle file and `<management-vip>` with the VIP address of the {props.version} management cluster. If you have changed the default port or the base content path for the Zot registry, replace `30003` with the correct port number and `spectro-content` with the correct content path.
 
-   If you are using custom TLS certificates or choosing to skip TLS, use the appropriate flags as shown below.
+   If you are using custom TLS certificates or choosing to skip TLS, use the appropriate flags as shown in the following examples.
 
-   <Tabs>
+   <Tabs groupId="tls-palette-cli">
 
    <TabItem label="Custom TLS Certificate" value="custom-tls-certificate">
 
@@ -139,15 +139,15 @@ partial_name: upload-packs-enablement
 5. Authenticate with your external registry using the command line or a GUI tool of your choice. The following examples
    demonstrate how to authenticate with an OCI registry using the [`oras`](https://oras.land/docs/) CLI tool and the Palette CLI.
 
-   <Tabs>
+   <Tabs groupId="external-registry-type">
 
    <TabItem label="Harbor" value="harbor">
 
    Use `oras` to log in to your OCI registry. Replace the values below with your environment configuration values.
    If you are using a Harbor registry with a self-signed certificate, add the `--insecure` flag to the
    `oras` command.
 
-   <Tabs>
+   <Tabs groupId="tls-harbor">
 
    <TabItem label="Regular Certificate" value="regular-certificate">
 
@@ -176,7 +176,7 @@ partial_name: upload-packs-enablement
    [AWS ECR Authentication](https://docs.aws.amazon.com/AmazonECR/latest/userguide/getting-started-cli.html#cli-authenticate-registry)
    documentation for more information.
 
-   <Tabs>
+   <Tabs groupId="ecr-type">
 
    <TabItem label="Private ECR" value="private-ecr">
 
@@ -221,11 +221,11 @@ partial_name: upload-packs-enablement
 
 6. Upload the pack bundles to the OCI registry. The following example commands upload a pack bundle to the OCI registry in the `spectro-content` base path. Replace the values below with your environment configuration values.
 
-   <Tabs>
+   <Tabs groupId="external-registry-type">
 
-   <TabItem label="Harbor" value="harbor-upload">
+   <TabItem label="Harbor" value="harbor">
 
-   <Tabs>
+   <Tabs groupId="tls-harbor">
 
    <TabItem label="Regular Certificate" value="regular-certificate">
 
@@ -247,7 +247,7 @@ partial_name: upload-packs-enablement
 
    </TabItem>
 
-   <TabItem label="AWS ECR" value="aws-ecr-upload">
+   <TabItem label="AWS ECR" value="aws-ecr">
 
    ```shell
    oras push <aws-ecr-url>/spectro-content/<repository-name>:<tag> --file <path-to-pack-bundle-zst>
@@ -259,9 +259,9 @@ partial_name: upload-packs-enablement
 
    Upload the pack bundles to your external registry using the Palette CLI. Replace `<pack-zst>` with your downloaded pack bundle file, `<registry-dns-or-ip>` with the DNS/IP address of your registry, and `<registry-port>` with the port number of your registry. If you have changed the base content path from the default, replace `spectro-content` with the correct content path.
 
-   If you are using custom TLS certificates or choosing to skip TLS, use the appropriate flags as shown below.
+   If you are using custom TLS certificates or choosing to skip TLS, use the appropriate flags as shown in the following examples.
 
-   <Tabs>
+   <Tabs groupId="tls-palette-cli">
 
    <TabItem label="Custom TLS Certificate" value="custom-tls-certificate">
 

@@ -20,11 +20,11 @@ partial_name: upload-packs-validate
 
 1. Use the following example `oras` commands to list the repositories in the OCI registry under the `spectro-content` base path. If you have changed the base content path from the default, replace `spectro-content` with the correct content path. Replace the remaining templated values with your environment configuration values.
 
-   <Tabs>
+   <Tabs groupId="external-registry-type">
 
-   <TabItem label="Harbor" value="harbor-list">
+   <TabItem label="Harbor" value="harbor">
 
-   <Tabs>
+   <Tabs groupId="tls-harbor">
 
    <TabItem label="Regular Certificate" value="regular-certificate">
 
@@ -46,7 +46,7 @@ partial_name: upload-packs-validate
 
    </TabItem>
 
-   <TabItem label="AWS ECR" value="aws-ecr-list">
+   <TabItem label="AWS ECR" value="aws-ecr">
 
    ```shell
    oras repo ls <aws-ecr-url>/spectro-content

@@ -7,7 +7,7 @@ partial_name: upload-third-party-packs-enablement
 
 <TabItem value="internal-zot-registry" label="Internal Zot Registry">
 
-<Tabs>
+<Tabs groupId="upload-method">
 
 <TabItem label="Local UI Method" value="local-ui-method">
 
@@ -45,7 +45,7 @@ partial_name: upload-third-party-packs-enablement
    The upload process starts automatically once the files are selected. You can monitor the upload progress in
    the **Upload Content** dialog.
 
-   Wait for the **Upload Successful** confirmation message to appear.
+   Wait for the **File(s) uploaded successfully** confirmation message or the green check mark to appear next to the upload progress bar.
 
 10. Log in to the {props.version} system console.
 
@@ -91,9 +91,9 @@ partial_name: upload-third-party-packs-enablement
 
 6. Upload the packs to the internal Zot registry using the Palette CLI. Replace `<third-party-zst>` and `<third-party-conformance-zst>` with your downloaded Third Party pack ZST files and `<management-vip>` with the VIP address of the {props.version} management cluster. If you have changed the default port or the base content path for the Zot registry, replace `30003` with the correct port number and `spectro-content` with the correct content path.
 
-   If you are using custom TLS certificates or choosing to skip TLS, use the appropriate flags as shown below.
+   If you are using custom TLS certificates or choosing to skip TLS, use the appropriate flags as shown in the following examples.
 
-   <Tabs>
+   <Tabs groupId="tls-palette-cli">
 
    <TabItem label="Custom TLS Certificate" value="custom-tls-certificate">
 
@@ -188,15 +188,15 @@ partial_name: upload-third-party-packs-enablement
 7. Authenticate with your external registry using the command line or a GUI tool of your choice. The following examples
    demonstrate how to authenticate with an OCI registry using the [`oras`](https://oras.land/docs/) CLI tool and the Palette CLI.
 
-   <Tabs>
+   <Tabs groupId="external-registry-type">
 
    <TabItem label="Harbor" value="harbor">
 
    Use `oras` to log in to your OCI registry. Replace the values below with your environment configuration values.
    If you are using a Harbor registry with a self-signed certificate, add the `--insecure` flag to the
    `oras` command.
 
-   <Tabs>
+   <Tabs groupId="tls-harbor">
 
    <TabItem label="Regular Certificate" value="regular-certificate">
 
@@ -225,7 +225,7 @@ partial_name: upload-third-party-packs-enablement
    [AWS ECR Authentication](https://docs.aws.amazon.com/AmazonECR/latest/userguide/getting-started-cli.html#cli-authenticate-registry)
    documentation for more information.
 
-   <Tabs>
+   <Tabs groupId="ecr-type">
 
    <TabItem label="Private ECR" value="private-ecr">
 
@@ -270,11 +270,11 @@ partial_name: upload-third-party-packs-enablement
 
 8. Upload the packs to the OCI registry. The following example commands upload the packs to the OCI registry in the `spectro-content` base path. Replace the values below with your environment configuration values.
 
-   <Tabs>
+   <Tabs groupId="external-registry-type">
 
-   <TabItem label="Harbor" value="harbor-upload">
+   <TabItem label="Harbor" value="harbor">
 
-   <Tabs>
+   <Tabs groupId="tls-harbor">
 
    <TabItem label="Regular Certificate" value="regular-certificate">
 
@@ -304,7 +304,7 @@ partial_name: upload-third-party-packs-enablement
 
    </TabItem>
 
-   <TabItem label="AWS ECR" value="aws-ecr-upload">
+   <TabItem label="AWS ECR" value="aws-ecr">
 
    ```shell title="Upload Third Party Pack to AWS ECR"
    oras push <aws-ecr-url>/spectro-content/<repository-name>:<tag> --file <path-to-third-party-zst>
@@ -320,9 +320,9 @@ partial_name: upload-third-party-packs-enablement
 
    Upload the packs to your external registry using the Palette CLI. Replace `<third-party-zst>` and `<third-party-conformance-zst>` with your downloaded pack bundle files, `<registry-dns-or-ip>` with the DNS/IP address of your registry, and `<registry-port>` with the port number of your registry. If you have changed the base content path from the default, replace `spectro-content` with the correct content path.
 
-   If you are using custom TLS certificates or choosing to skip TLS, use the appropriate flags as shown below.
+   If you are using custom TLS certificates or choosing to skip TLS, use the appropriate flags as shown in the following examples.
 
-   <Tabs>
+   <Tabs groupId="tls-palette-cli">
 
    <TabItem label="Custom TLS Certificate" value="custom-tls-certificate">
 

@@ -21,7 +21,7 @@ partial_name: upload-third-party-packs-validate
 
    <Tabs>
 
-   <TabItem label="Harbor" value="harbor-list">
+   <TabItem label="Harbor" value="harbor">
 
    <Tabs>
 
@@ -45,7 +45,7 @@ partial_name: upload-third-party-packs-validate
 
    </TabItem>
 
-   <TabItem label="AWS ECR" value="aws-ecr-list">
+   <TabItem label="AWS ECR" value="aws-ecr">
 
    ```shell
    oras repo ls <aws-ecr-url>/spectro-content

@@ -4060,6 +4060,10 @@
         "nodeRole": {
           "$ref": "#/definitions/v1NodeRole"
         },
+        "overlayIP": {
+          "description": "edge host overlay ip",
+          "type": "string"
+        },
         "role": {
           "description": "edge host role",
           "type": "string"
@@ -4193,12 +4197,7 @@
           "type": "string"
         },
         "type": {
-          "description": "Management type (local/remote)",
-          "type": "string",
-          "enum": [
-            "local",
-            "remote"
-          ]
+          "$ref": "#/definitions/v1ManagementMode"
         }
       }
     },
@@ -4232,6 +4231,7 @@
           "type": "string"
         },
         "labels": {
+          "description": "Labels are key-value pairs that can be used to organize and categorize resources.\n",
           "type": "object",
           "additionalProperties": {
             "type": "string"
@@ -4989,6 +4989,9 @@
         "archiveUploadPath": {
           "type": "string"
         },
+        "metadata": {
+          "$ref": "#/definitions/v1MetaData"
+        },
         "variables": {
           "type": "array",
           "items": {