Alauda Hyperflux
  • English

    • Upgrade

    This document provides instructions for upgrading Alauda Hyperflux to a newer version.

    TOC

    Standard Upgrade StepsUpgrading from v1.2.0 to v1.2.1 (Special Case)Step 1: Backup Knowledge BaseStep 2: Execute UpgradeStep 3: Restore Knowledge Base

    Standard Upgrade Steps

    For most version upgrades (except for v1.2.0 to v1.2.1), you can simply follow these steps in the ACP console:

    1. Upload the new version of the plugin package to the ACP Marketplace. Upload the package in the same way as the initial installation. After the upload is complete, wait for approximately 10–15 minutes for the platform to automatically synchronize the new version information.
    2. Verify that the new version is available in the Marketplace. Go to Administrator / Marketplace / Upload Packages. Switch to the Cluster Plugin tab and confirm that the new version number is displayed for the Hyperflux plugin.
    3. Execute the upgrade operation on the cluster. Navigate to Administrator / Clusters / Clusters. Find the cluster where the Hyperflux plugin is installed; an upgrade icon will be displayed in the cluster entry. Click to enter the cluster details, and switch to the Features tab. On the Hyperflux plugin card, click the Upgrade button and confirm the operation.
    4. Verify the upgrade result. After the upgrade is complete, confirm that the version number has been updated in the Features tab. Verify normal operation through plugin status monitoring or logs.

    Upgrading from v1.2.0 to v1.2.1 (Special Case)

    IMPORTANT: Upgrading from v1.2.0 to v1.2.1 will cause the knowledge base to be re-initialized. You must manually back up and restore your database to prevent data loss.

    Step 1: Backup Knowledge Base

    Before performing the upgrade, execute the following commands:

    # Get the PostgreSQL pod name (if using the built-in database)
kubectl -n cpaas-system get pod | grep postgre-vec

# Dump the database to a file
kubectl -n cpaas-system exec -it <postgre-vec-xxx> -- pg_dump -U postgres -d <your-database-name> -F c -f /tmp/hyperflux_backup.dump

# Copy the dump file to your local machine
kubectl -n cpaas-system cp <postgre-vec-xxx>:/tmp/hyperflux_backup.dump ./hyperflux_backup.dump

    Step 2: Execute Upgrade

    Follow the Standard Upgrade Steps described above to upgrade the plugin version through the ACP console.

    Step 3: Restore Knowledge Base

    After the upgrade is complete, restore your data:

    # Get the new PostgreSQL pod name
kubectl -n cpaas-system get pod | grep postgre-vec

# Copy the backup dump file back to the pod
kubectl -n cpaas-system cp ./hyperflux_backup.dump <postgre-vec-xxx>:/tmp/hyperflux_backup.dump

# Restore the database from the dump file
kubectl -n cpaas-system exec -it <postgre-vec-xxx> -- pg_restore -U postgres -d <your-database-name> /tmp/hyperflux_backup.dump

# (Optional) Update configuration if your database/collection name changed
kubectl -n cpaas-system edit configmap smart-doc-config
# Update `PG_CONN_DB` and `PG_COLLECTION_NAME` fields if necessary.

    Wait for the Alauda Hyperflux pods to restart and verify that the knowledge base has been restored successfully.