Merge branch 'master' into docs-rel-4-8-0

Author: addetz

.gitignore

@@ -76,6 +76,8 @@ artifact.zip
 .netlify/
 # Ignore _partials/index.ts
 _partials/index.ts
+_partials/breaking-changes/*
+src/components/ReleaseNotesBreakingChanges/versions.json
 
 # Ignore statoc/img/packs
 static/img/packs

Makefile

@@ -335,6 +335,7 @@ find-unused-images:
 ###@ Generate _partials/index.ts required to automatic partials usage.
 
 generate-partials: ## Generate
+	./scripts/index-breaking-changes.sh
 	./scripts/generate-partials.sh
 
 ###@ Fetch cached packs assets.

_partials/self-hosted/management-appliance/_upgrade-palette-prereqs.mdx

@@ -21,11 +21,11 @@ partial_name: upgrade-palette-prereqs
 
 - Check that your upgrade path is supported by referring to the <PaletteVertexUrlMapper edition={props.edition} text="Supported Upgrade Paths" url="/upgrade#supported-upgrade-paths"/>.
 
-- If upgrading from version **4.7.15**, you must run an additional script to prepare {props.version} for the upgrade.
+- If upgrading from version **4.7.15**, you must run an additional script before upgrading {props.version}. This script changes the access mode of the `zot` deployment's PersistentVolumeClaim (PVC) from `RWX` (ReadWriteMany) to `RWO` (ReadWriteOnce), which is required for the upgrade process.
 
   <details>
 
-  <summary> Click to expand the instructions for the script </summary>
+  <summary> Click to expand the instructions for the 4.7.15 script </summary>
 
   1. Log in to Local UI of the leader node of your Palette management cluster. For example, `https://<palette-leader-node-ip>:5080`.
 
@@ -302,4 +302,222 @@ partial_name: upgrade-palette-prereqs
       zot-c96cb7b-hspd2   1/1     Running   0          5m3s
       ```
 
+  </details>
+
+- If upgrading from version **4.7.27**, you must run an additional script before upgrading {props.version}. This script ensures the `linstor-lvm-storage` StorageClass has correct parameters and safely recreates the PVC while preserving data.
+
+  <details>
+
+  <summary> Click to expand the instructions for the 4.7.27 script </summary>
+
+  1. Log in to Local UI of the leader node of your Palette management cluster. For example, `https://<palette-leader-node-ip>:5080`.
+
+  2. From the left main menu, click **Cluster**.
+
+  3. On the **Overview** tab, within the **Environment** section, click the link for the **Admin Kubeconfig File** to download the kubeconfig file.
+
+  4. On your local machine, ensure you have `kubectl` installed and set the `KUBECONFIG` environment variable to point to the file.
+
+     ```bash
+     export KUBECONFIG=/path/to/downloaded/kubeconfig/file
+     ```
+
+  5. Use the following command to create a script named `recreate.sh`.
+
+     The script ensures that the `linstor-lvm-storage` StorageClass has the correct parameters (`resourceGroup: lvm-ha` and `placementCount: 3`). If the StorageClass does not exist or has different parameters, it recreates it. Then, it safely recreates a specified PVC to bind to a new PV while preserving data, handling deployments with `volumeBindingMode=WaitForFirstConsumer` by scaling down the deployment first.
+
+     ```bash
+     cat > recreate.sh <<'SCRIPT'
+     #!/bin/bash
+     # Recreate a PVC with updated StorageClass configuration
+     # Ensures the linstor-lvm-storage StorageClass exists with correct parameters,
+     # then recreates the specified PVC which may bind to a new PV.
+     # Safely handles volumeBindingMode=WaitForFirstConsumer by scaling down the deployment first.
+
+     set -euo pipefail
+
+     NAMESPACE=${1:-zot-system}
+     PVC_NAME=${2:-zot-pvc}
+     DEPLOY_NAME=${3:-zot}
+
+
+     #!/bin/bash
+     set -e
+
+     SC_NAME="linstor-lvm-storage"
+
+     echo "Checking for existing StorageClass '$SC_NAME'..."
+
+     if kubectl get storageclass $SC_NAME >/dev/null 2>&1; then
+       echo "StorageClass '$SC_NAME' exists. Checking parameters..."
+
+       CURRENT_RG=$(kubectl get storageclass $SC_NAME -o jsonpath='{.parameters.resourceGroup}')
+       CURRENT_PC=$(kubectl get storageclass $SC_NAME -o jsonpath='{.parameters.placementCount}')
+
+       if [[ "$CURRENT_RG" == "lvm-ha" && "$CURRENT_PC" == "3" ]]; then
+         echo "✅ StorageClass already has resourceGroup='lvm-ha' and placementCount='3'. Skipping re-creation."
+       else
+         echo "StorageClass parameters differ (resourceGroup=$CURRENT_RG, placementCount=$CURRENT_PC). Recreating..."
+         kubectl delete storageclass $SC_NAME
+         echo "Recreating StorageClass '$SC_NAME'..."
+         cat <<EOF | kubectl apply -f -
+     apiVersion: storage.k8s.io/v1
+     kind: StorageClass
+     metadata:
+       name: $SC_NAME
+       annotations:
+         storageclass.kubernetes.io/is-default-class: "false"
+         helm.sh/hook: post-install,post-upgrade
+     provisioner: linstor.csi.linbit.com
+     parameters:
+       placementCount: "3"
+       resourceGroup: "lvm-ha"
+       storagePool: "lvm-thin"
+     reclaimPolicy: Delete
+     volumeBindingMode: WaitForFirstConsumer
+     allowVolumeExpansion: true
+     EOF
+         echo "✅ StorageClass '$SC_NAME' updated."
+       fi
+     else
+       echo "StorageClass not found. Creating new one..."
+       cat <<EOF | kubectl apply -f -
+     apiVersion: storage.k8s.io/v1
+     kind: StorageClass
+     metadata:
+       name: $SC_NAME
+       annotations:
+         storageclass.kubernetes.io/is-default-class: "false"
+         helm.sh/hook: post-install,post-upgrade
+     provisioner: linstor.csi.linbit.com
+     parameters:
+       placementCount: "3"
+       resourceGroup: "lvm-ha"
+       storagePool: "lvm-thin"
+     reclaimPolicy: Delete
+     volumeBindingMode: WaitForFirstConsumer
+     allowVolumeExpansion: true
+     EOF
+       echo "✅ StorageClass '$SC_NAME' created."
+     fi
+
+     echo "Getting PV bound to PVC '${PVC_NAME}' in namespace '${NAMESPACE}'..."
+     PV_NAME=$(kubectl get pvc -n "${NAMESPACE}" "${PVC_NAME}" -o jsonpath='{.spec.volumeName}' 2>/dev/null || true)
+     if [ -z "${PV_NAME}" ]; then
+       echo "❌ PVC '${PVC_NAME}' not found or not bound to any PV."
+       exit 1
+     fi
+     echo "Found PV: ${PV_NAME}"
+
+     echo "Scaling down deployment '${DEPLOY_NAME}' to release PVC..."
+     kubectl scale deploy "${DEPLOY_NAME}" -n "${NAMESPACE}" --replicas=0 || true
+
+     echo "Deleting PVC '${PVC_NAME}' (PV data will be retained)..."
+     kubectl delete pvc -n "${NAMESPACE}" "${PVC_NAME}" --ignore-not-found
+
+     STORAGE=$(kubectl get pv "${PV_NAME}" -o jsonpath='{.spec.capacity.storage}')
+     ACCESSMODES=$(kubectl get pv "${PV_NAME}" -o jsonpath='{.spec.accessModes[0]}')
+
+     echo "Recreating PVC '${PVC_NAME}' bound to existing PV '${PV_NAME}'..."
+     cat <<EOF | kubectl apply -f -
+     apiVersion: v1
+     kind: PersistentVolumeClaim
+     metadata:
+       name: ${PVC_NAME}
+       namespace: ${NAMESPACE}
+     spec:
+       accessModes:
+         - ${ACCESSMODES}
+       storageClassName: linstor-lvm-storage
+       resources:
+         requests:
+           storage: ${STORAGE}
+     EOF
+
+     echo "Scaling deployment '${DEPLOY_NAME}' back up..."
+     kubectl scale deploy "${DEPLOY_NAME}" -n "${NAMESPACE}" --replicas=1 || true
+
+     echo "Waiting for PVC '${PVC_NAME}' to rebind..."
+     for i in {1..30}; do
+       STATUS=$(kubectl get pvc -n "${NAMESPACE}" "${PVC_NAME}" -o jsonpath='{.status.phase}' 2>/dev/null || echo "")
+       if [[ "$STATUS" == "Bound" ]]; then
+         echo "✅ PVC successfully bound."
+         break
+       fi
+       sleep 2
+     done
+
+     # Get the new PV name after PVC is bound
+     NEW_PV_NAME=$(kubectl get pvc -n "${NAMESPACE}" "${PVC_NAME}" -o jsonpath='{.spec.volumeName}' 2>/dev/null || echo "")
+     if [ -z "${NEW_PV_NAME}" ]; then
+       echo "Warning: Could not determine new PV name."
+       NEW_PV_NAME="<check manually>"
+     fi
+
+     echo "Done!"
+     echo "✅ PVC '${PVC_NAME}' is bound to PV '${NEW_PV_NAME}' and data preserved."
+     echo "
+     Verify with:
+       kubectl get pvc -n ${NAMESPACE} ${PVC_NAME}
+       kubectl get pv ${NEW_PV_NAME}
+     "
+     SCRIPT
+     ```
+
+  6. Make the script executable.
+  
+     ```bash
+     chmod u+x recreate.sh
+     ```   
+
+  7. Use the following command to execute the script.
+
+     ```bash
+     ./recreate.sh
+     ```
+
+     ```shell hideClipboard title="Example output"
+     Checking for existing StorageClass 'linstor-lvm-storage'...
+     StorageClass 'linstor-lvm-storage' exists. Checking parameters...
+     ✅ StorageClass already has resourceGroup='lvm-ha' and placementCount='3'. Skipping re-creation.
+     Getting PV bound to PVC 'zot-pvc' in namespace 'zot-system'...
+     Found PV: pvc-3b7a8f9c-1d2e-4f5a-9b0c-1a2b3c4d5e6f
+     Scaling down deployment 'zot' to release PVC...
+     deployment.apps/zot scaled
+     Deleting PVC 'zot-pvc' (PV data will be retained)...
+     persistentvolumeclaim "zot-pvc" deleted
+     Recreating PVC 'zot-pvc' bound to existing PV 'pvc-3b7a8f9c-1d2e-4f5a-9b0c-1a2b3c4d5e6f'...
+     persistentvolumeclaim/zot-pvc created
+     Scaling deployment 'zot' back up...
+     deployment.apps/zot scaled
+     Waiting for PVC 'zot-pvc' to rebind...
+     ✅ PVC successfully bound.
+     Done!
+     ✅ PVC 'zot-pvc' is bound to PV 'pvc-7e9d2a10-4a6b-431f-b9e7-8c2d1f3a5b6c' and data preserved.
+
+     Verify with:
+       kubectl get pvc -n zot-system zot-pvc
+       kubectl get pv pvc-7e9d2a10-4a6b-431f-b9e7-8c2d1f3a5b6c
+     ```
+
+  8. Verify that the PVC and PV status is `Bound`.
+
+     ```bash
+     kubectl get pvc --namespace zot-system zot-pvc
+     ```
+
+     ```shell hideClipboard title="Example output"
+     NAME      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS          VOLUMEATTRIBUTESCLASS   AGE
+     zot-pvc   Bound    pvc-7e9d2a10-4a6b-431f-b9e7-8c2d1f3a5b6c   300Gi      RWO            linstor-lvm-storage   <unset>                 5m30s
+     ```
+
+     ```bash
+     kubectl get pv pvc-7e9d2a10-4a6b-431f-b9e7-8c2d1f3a5b6c
+     ```
+
+     ```shell hideClipboard title="Example output"
+     NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                    STORAGECLASS          REASON   AGE
+     pvc-7e9d2a10-4a6b-431f-b9e7-8c2d1f3a5b6c   300Gi      RWO            Delete           Bound    zot-system/zot-pvc       linstor-lvm-storage            5m30s
+     ```
+
   </details>

docs/docs-content/cluster-templates/create-cluster-template-policies/maintenance-policy.md

@@ -110,13 +110,19 @@ cluster templates.
 9.  When finished, **Confirm** your schedule.
 
 10. Your schedule appears in the **Upgrade schedule** section of the **Basic information** window. If you would like to
-    add additional schedules, select **Add Schedule**, and repeat steps 5 - 10; otherwise, select **Next**.
+    add additional schedules, select **Add Schedule**, and repeat steps 5 - 10. When you are finished adding schedules,
+    select **Next**.
 
-    :::tip
+    :::info
 
-    Each template can be linked to one maintenance policy only. All schedules attached to a maintenance policy are
-    initiated on the attached clusters during the specified upgrade window. If you do not want all schedules applied to
-    certain clusters, consider making another maintenance policy and attaching it to a separate cluster template.
+    - If you have multiple schedules for the same maintenance policy, the upgrade windows cannot overlap. For example,
+      if one schedule begins at 8:00 AM on Sunday with a three-hour upgrade window, and another schedule begins at 10:00
+      AM on Sunday with a three-hour upgrade window, the upgrade windows overlap at 10:00 AM, and you will receive an
+      error when attempting to **Finalize** your maintenance policy.
+
+    - Each template can be linked to one maintenance policy only. All schedules attached to a maintenance policy are
+      initiated on the attached clusters during the specified upgrade window. If you do not want all schedules applied
+      to certain clusters, consider creating another maintenance policy and attaching it to a separate cluster template.
 
     :::
 

docs/docs-content/downloads/artifact-studio.md

@@ -113,7 +113,7 @@ Agent mode binaries cannot be downloaded at this time.
 
    :::
 
-   ![Image of Create pack bundle](../../../static/assets/docs/images/downloads/downloads_artifact-studio-build-bundle-4-7-a.webp)
+   ![Image of Create pack bundle](../../../static/assets/docs/images/downloads/downloads_artifact-studio-build-bundle-4-7-45.webp)
 
 3. On the **Select Product** page, select either **Palette Enterprise Appliance** or **Palette Vertex Appliance**.
 
@@ -136,13 +136,18 @@ Agent mode binaries cannot be downloaded at this time.
    Data centers include **MAAS**, **OpenStack**, and **vSphere**.
 
 7. On the **Configure bundle** page, select the **OS** layer to begin building your bundle. Only the packs compatible
-   with your previous selections are displayed. Choose an operating system and select **Next Layer**.
+   with your previous selections are displayed. Choose an operating system and use the **Select option** drop-down menu
+   to choose the desired version of your pack. Once selected, the pack appears in the **Selected items** pane on the
+   right. Select **Next Layer**.
 
-8. Choose your Kubernetes distribution and version and select **Next Layer**.
+8. Choose your Kubernetes distribution and use the **Select option** drop-down menu to choose the desired version of
+   your pack. Once selected, the pack appears in the **Selected items** pane on the right. Select **Next Layer**.
 
-9. Choose your networking pack and select **Next Layer**.
+9. Choose your networking pack and use the **Select option** drop-down menu to choose the desired version of your pack.
+   Once selected, the pack appears in the **Selected items** pane on the right. Select **Next Layer**.
 
-10. Choose your storage pack and select **Next Layer**.
+10. Choose your storage pack and use the **Select option** drop-down menu to choose the desired version of your pack.
+    Once selected, the pack appears in the **Selected items** pane on the right. Select **Next Layer**.
 
 11. Add additional packs to your bundle as needed. When finished, select **Add to Bundle**.
 
@@ -170,13 +175,18 @@ infrastructure type of **Edge Native** is assumed.
 :::
 
 6. On the **Configure bundle** page, select the **OS** layer to begin building your bundle. Only the packs compatible
-   with your previous selections are displayed in each layer. Choose an operating system and select **Next Layer**.
+   with your previous selections are displayed in each layer. Use the **Select option** drop-down menu to choose the
+   desired version of your pack. Once selected, the pack appears in the **Selected items** pane on the right. Choose an
+   operating system and select **Next Layer**.
 
-7. Choose your Kubernetes distribution and version and select **Next Layer**.
+7. Choose your Kubernetes distribution and use the **Select option** drop-down menu to choose the desired version of
+   your pack. Once selected, the pack appears in the **Selected items** pane on the right. Select **Next Layer**.
 
-8. Choose your networking pack and select **Next Layer**.
+8. Choose your networking pack and use the **Select option** drop-down menu to choose the desired version of your pack.
+   Once selected, the pack appears in the **Selected items** pane on the right. Select **Next Layer**.
 
-9. Choose your storage pack and select **Next Layer**.
+9. Choose your storage pack and use the **Select option** drop-down menu to choose the desired version of your pack.
+   Once selected, the pack appears in the **Selected items** pane on the right. Select **Next Layer**.
 
 10. Add additional packs to your bundle as needed. When finished, select **Add to Bundle**.
 
@@ -196,7 +206,9 @@ infrastructure type of **Edge Native** is assumed.
 <TabItem label="Add-On" value="addon">
 
 6. When you select **Add-on only**, you are automatically taken to the **Configure bundle** page. Here, you can search
-   for and select any packs you want to download. Select **Next Step** once you have selected your desired packs.
+   for and select any packs you want to download. Use the **Select option** drop-down menu to choose the desired version
+   of your pack. Once selected, the pack appears in the **Selected items** pane on the right. Select **Next Step** once
+   you have selected your desired packs.
 
 7. Confirm that the bundle specifications and content are correct. If you need to make any changes, return to the
    applicable page using the left menu. To add additional packs, select **Explore additional add-ons**.
@@ -222,26 +234,25 @@ information on how to verify the authenticity and integrity of your bundles, ref
 
 2. In the **Create pack bundle** section, select **Browse Packs**.
 
-   ![Image showing where to download individual packs](../../../static/assets/docs/images/downloads/downloads_artifact-studio-browse-packs-4-7-a.webp)
+   ![Image showing where to download individual packs](../../../static/assets/docs/images/downloads/downloads_artifact-studio-browse-packs-4-7-45.webp)
 
 3. On the left menu, choose any applicable pack filters, such as **Product**, product **Version**, **Cloud type**, and
    **Layer type**. Beside the search bar are additional filters: infrastructure type (**AMD64** or **ARM64**), and FIPS
    compliance (FIPS or non-FIPS).
 
 4. After you have applied any necessary filters, navigate through the list of packs. Use the **Search** bar to filter
-   your results further.
+   your results further. Use the **Select option** drop-down menu to choose the desired version of your pack. Once
+   selected, the pack appears in the **Selected items** pane on the right.
 
-   ![Image showing filter and search together](../../../static/assets/docs/images/downloads/downloads_artifact-studio-search-and-filter-4-7-a.webp)
+   ![Image showing download of multiple packs](../../../static/assets/docs/images/downloads/downloads_artifact-studio-ind-packs-dl-4-7-2025-45.webp)
 
-5. When finished, select the **I'm not a robot** reCAPTCHA checkbox, and select **Download Bundle**. Alternatively, you
-   can **Copy all URLs** so that you can download the applicable files later in an alternate manner of your choosing,
-   such as via `curl`.
+5. Repeat step 4 until you have added all necessary packs. When finished, select the **I'm not a robot** reCAPTCHA
+   checkbox, and select **Download Bundle**. Alternatively, you can **Copy all URLs** so that you can download the
+   applicable files later in an alternate manner of your choosing, such as via `curl`.
 
 6. The download begins. Each pack is downloaded as an individual ZST file (`<pack-name>.zst`) with an accompanying
    signature file (`<pack-name>.sig.bin`).
 
-   ![Image showing download of multiple packs](../../../static/assets/docs/images/downloads/downloads_artifact-studio-individual-packs-download-4-7-a.webp)
-
    :::tip
 
    Ensure that pop-ups are enabled in your browser for [Artifact Studio](https://artifact-studio.spectrocloud.com/) to

docs/docs-content/enterprise-version/upgrade/upgrade.md

@@ -36,6 +36,9 @@ Refer to the following tables for the supported self-hosted Palette upgrade path
 Before upgrading Palette to a new major version, you must first update it to the latest patch version of the latest
 minor version available.
 
+Use the [Find Breaking Changes](../../release-notes/breaking-changes.md) page to list all the breaking changes between
+Palette versions. Ensure that you have addressed all changes before upgrading Palette.
+
 :::
 
 :::warning