This guide details the upgrade strategy and procedures for Alauda DevOps to Alauda DevOps (Next-Gen) when migrating from Alauda Container Platform v3.18 or v4.0 to v4.1.
First, upgrade the ACP platform to version v4.1. For detailed instructions, refer to .
Before migration, ensure that Alauda DevOps is upgraded to version v3.20. This step is required for compatibility and successful migration to Alauda DevOps (Next-Gen). Please refer to Upgrading Alauda DevOps to v3.20
Starting from ACP v4.1, the following Alauda DevOps v3 operators will no longer be maintained, so completing the migration on ACP v4.1 is necessary.
| Operator | Status |
|---|---|
| Alauda DevOps Tekton v3 | End-of-life |
| Alauda DevOps GitLab v3 | End-of-life |
| Alauda DevOps Harbor v3 | End-of-life |
| Alauda DevOps SonarQube v3 | End-of-life |
| Alauda DevOps Nexus v3 | End-of-life |
| Alauda DevOps Operator | Version |
|---|---|
| Alauda DevOps Pipelines | v4.0.z |
| Alauda Build of Gitlab | v17.8.z |
| Alauda Build of Harbor | v2.12.z |
| Alauda Build of SonarQube | v2025.1.z |
| Alauda Build of Nexus | v3.76.z |
The .z in version numbers indicates the latest available patch version for that minor release. During upgrade, you should always use the latest patch version to benefit from the most recent security updates and bug fixes.
violet tool to upload Operators toACP, For specific operation steps, refer to .Please refer to the following documents for migrating each operator:
You have now completed the migration from Alauda DevOps to Alauda DevOps (Next Generation). 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.