#Pre-Upgrade Preparation

Supported upgrade paths:

• From 4.0 → 4.2
• From 4.1 → 4.2

Before starting, ensure your current platform version is within the supported upgrade range.

#Important Notes

• Ensure the directory /cpaas/minio on the control plane nodes of global cluster has at least 120 GB of free disk space.
• Make sure that ALL clusters are running Kubernetes versions within the supported range. See details below.

#Kubernetes prerequisites

#Run the Checklist

Contact technical support to obtain the checklist script and run it against the target platform to verify upgrade readiness.

#Download the Packages

From the Customer Portal, download the Core Package.

If you want to upgrade cluster Extensions during the upgrade, follow these steps:

1. Navigate to the CLI Tools section in the Customer Portal and download the violet tool. This tool is required for uploading Extensions. For more information about violet, see Upload Packages.

2. On any machine with network access to the platform endpoint, run violet list to list the extensions in the current environment and export the output to ./apps.yaml.

   violet list \
     --platform-address "https://<your-platform-domain>" \
     --platform-token "<platform_token>" \
     --output-file "./apps.yaml"

   Prefer --platform-token over --platform-password to avoid exposing passwords in shell history and process listings (ps aux).

3. Import the exported apps.yaml file into the Customer Portal to align the extension list.

violet push <path/to/directory/only_put_topolvm_plugin_here> \
  --target-catalog-source "platform" \
  --platform-address "https://example.com" \
  --platform-username "<platform_user>" \
  --platform-password "<platform_password>" \
  --clusters "<cluster_name>"
  --platform-token "<platform_token>" \
  --clusters "cluster-a,cluster-b"