Overview
This guide provides a detailed introduction to the upgrade/migration strategy of Alauda DevOps in the scenario of upgrading from Alauda Container Platform (ACP) v4.0 or v4.1 to v4.2.
Upgrade Scenarios
If your current ACP version is v4.0, the upgrade path for Alauda DevOps is as follows:
-
Migrate to Alauda DevOps (Next-Gen)
Before upgrading ACP, verify your current DevOps operator versions:
- If your operators do not match the Alauda DevOps (Next-Gen) Version Matrix, you must perform migration by following Migrating Alauda DevOps to Alauda DevOps (Next-Gen).
- If you have already completed migration on
ACPv4.0and your operators match the Alauda DevOps (Next-Gen) Version Matrix, you may skip this step and proceed directly to ACP platform upgrade.
-
Upgrade ACP Platform
Upgrade the
ACPplatform to versionv4.2. For detailed instructions, refer to . -
Upgrade each operator to a newer version (optional)
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
TOC
Ensure that Alauda DevOps has been migrated to Alauda DevOps (Next-Gen)
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 (Next-Gen) version matrix after migration
Upgrade each operator to a newer version (optional)
You have now completed the migration from Alauda DevOps to Alauda DevOps (Next-Gen). In Alauda DevOps (Next-Gen), 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.
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.
References
For detailed upgrade and migration procedures, refer to: