Test automatic migration #1809
Description
Description
This test should cover the most straightforward migration from Turtles extension to Turtles installed as a Rancher system chart: upgrading Rancher to a version that installs Turtles as system chart. There's a section in the docs that describes this procedure: rancher/turtles-docs#378
The following is an example of the environment before and after migration:
Before
- Rancher
v2.12.2. - Turtles
v0.24.2- installed as a Rancher extension.
After
- Rancher
v2.13.1. - Turtles
v0.25.0- installed as a Rancher system chart.
In this post-upgrade scenario, there are multiple changes that should not affect the final functionality, including:
- Turtles is enabled by default in Rancher and embedded cluster api is disabled: https://github.com/rancher/rancher/pull/52067/files#diff-2f6213e2bd15bb256be4ed430e664c08612e86384445be797a20d5f56d48d101
- CAPI Providers, other than core API, are no longer shipped with Turtles (nor Rancher). If the existing installation had any
CAPIProviders, they should be migrated and the new chart should take ownership of them: see migration script.
Be aware that versions of Turtles before v0.24.2 do not add a Helm keep annotation to CAPIProvider resources: https://github.com/rancher/turtles/pull/1781/files#diff-594c8c61a723e07e0549e856c644d85a9c4c3ab14e22a14d411ce72687eedf2b. This means that if upgrading from any of these older versions, providers will be deleted.
Definition of done
The new test covers upgrading Rancher from v2.12.x to v2.13.x, which should automatically migrate Turtles installation seamlessly and adapt the configuration to the new chart structure with separate Turtles (only core CAPI) and CAPI Providers helm charts.