Alauda DevOps Docs

Overview

This guide provides a detailed introduction to the upgrade and migration strategy of Alauda DevOps in the following scenarios:

  • Upgrading Alauda Container Platform (ACP) from v4.0 to v4.3
  • Upgrading ACP from v4.1 to v4.3
  • Upgrading ACP from v4.2 to v4.3

TOC

Upgrade ScenariosEnsure that Alauda DevOps has been migrated to Alauda DevOps (Next-Gen)Alauda DevOps v3.20 version matrix before migrationAlauda DevOps (Next-Gen) version matrix after migrationUpgrade each operator to a newer versionReferences

Upgrade Scenarios

Upgrading from ACP v4.0
Upgrading from ACP v4.1
Upgrading from ACP v4.2

If your current ACP version is v4.0, the upgrade path for Alauda DevOps is as follows:

  1. Migrate to Alauda DevOps (Next-Gen)

    Before upgrading ACP, verify your current DevOps operator versions:

  2. Upgrade ACP Platform

    Upgrade the ACP platform to version v4.3. For detailed instructions, refer to Upgrading Container Platform.

  3. Upgrade each operator to a newer version

    If you want to use the updated version for each Operator, you can further learn how to upgrade to the updated version in each operator's documentation. Please refer to Upgrade each operator to a newer version.

Ensure that Alauda DevOps has been migrated to Alauda DevOps (Next-Gen)

This section applies to the historical upgrade paths for ACP v4.0 and v4.1. On ACP v4.0 or v4.1, ensure that Alauda DevOps has already been migrated to Alauda DevOps (Next-Gen). If your Alauda DevOps-related operators are at the versions listed below, you must perform the migration first. Please refer to Migrating Alauda DevOps to Alauda DevOps (Next-Gen).

Alauda DevOps v3.20 version matrix before migration

Alauda DevOps OperatorOperator VersionTool Instance Version
Alauda DevOps GitLab v3v3.20.zv14.0.z
Alauda DevOps Nexus v3v3.20.zv3.69.z
Alauda DevOps SonarQube v3v3.20.zv9.9.z
Alauda DevOps Harbor v3v3.20.zv2.6.z
Alauda DevOps Tekton v3v3.20.z-

Alauda DevOps (Next-Gen) version matrix after migration

Alauda DevOps OperatorVersion
Alauda DevOps Pipelines (replace Alauda DevOps Tekton v3)v4.0.z
Alauda Build of Gitlabv17.8.z
Alauda Build of Harborv2.12.z
Alauda Build of SonarQubev2025.1.z
Alauda Build of Nexusv3.76.z

Upgrade each operator to a newer version

After the ACP platform upgrade is completed, you can optionally upgrade the installed Alauda DevOps or Alauda DevOps (Next-Gen) Operators according to the scenario of your environment.

If you want to use the updated version for each installed Operator, refer to the corresponding documentation center and follow the approved channel and version for your target release.

Important

Each Operator must be upgraded to a version that is compatible with the current ACP version. Before upgrading an Operator, always confirm the supported version and compatibility requirements in the corresponding documentation.

Warning

Important Restriction

If you need to continue using the Build and Release features from Alauda DevOps v3, you must maintain Alauda DevOps Pipelines at version v4.0.z.

Prohibited Actions

Do NOT upgrade Alauda DevOps Pipelines beyond v4.0.z under any circumstances. Upgrading to versions above v4.0.z will cause irreversible compatibility issues with katanomi, potentially breaking existing Build and Release pipelines.

  1. Go to Administrator -> Marketplace -> Operator Hub.
  2. Switch to the target cluster.
  3. Open the details page of the corresponding Operator.
  4. Select the approved channel and version for the target release.
  5. Perform the upgrade and wait until the Operator status is healthy.

Upgrade only the installed components in your environment. Refer to the corresponding documentation center for the detailed procedure of each component:

References

For detailed upgrade and migration procedures, refer to: