Overview
When upgrading Alauda Container Platform (ACP) to v4.1, the upgrade strategy for Alauda DevOps depends on your current platform version. In all scenarios, migration to Alauda DevOps (Next-Gen) is mandatory to ensure platform security, maintainability, and compatibility with ACP v4.1.
Upgrade Scenarios
If your current ACP version is v3.18 , the Alauda DevOps upgrade path includes two required steps:
-
Upgrade
Alauda DevOpsto v3.20
This version ensures compatibility withACP v4.1and serves as the foundation for migration. -
Migrate
Alauda DevOpsto Alauda DevOps (Next-Gen)
Migration to the next-generation architecture is required to maintain platform security and long-term support.
Why Migration Is Mandatory
Migration to Alauda DevOps (Next-Gen) is required for the following reasons:
- Enhanced security, improved maintainability, and overall platform robustness.
- Starting from ACP v4.1, the following
Alauda DevOps v3Operators will reach end-of-life and will no longer be maintained or deployable:
| Operator Name | 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 |
Summary
| Step | Description | Required |
|---|---|---|
| Upgrade to v3.20 | Upgrade Alauda DevOps to version 3.20 to ensure compatibility with ACP v4.1. | ✅ Yes |
| Migrate to Next-Gen | Migrate to Alauda DevOps (Next-Gen) to enhance security and maintainability, and to meet ACP v4.1 requirements. | ✅ Yes |
References
For detailed upgrade and migration procedures, refer to: