Closed kkaempf closed 2 weeks ago
Additional set of PRs implementing this epic is in https://github.com/rancher/turtles/issues/478#issuecomment-2230965276
This included:
Out of band discovered and fixed issues present in previous releases of Turtles:
Description
After adding support for importing CAPI clusters into Rancher via the
clusters.management.cattle.io
(also known as v3.Cluster) resource (refer to PR), we would like to make this the default solution and deprecate the existing import mechanism, based onclusters.provisioning.cattle.io
.The default configuration of Turtles keeps the
v3
functionality behind a feature gatemanagementv3-cluster
and is only activated if explicitly specified, as its default value isfalse
.To Do
Fully migrating to using
v3
clusters means that we must:clusters.management.cattle.io
to the existingclusters.provisioning.cattle.io
: this means moving existing test suites to be based on the "new" Rancher cluster resource. This will also guarantee that the new Turtles controller works for every environment we're covering in E2E.provisioning.cattle.io
should be migrated tomanagement.cattle.io
transparently. Propose solution as a Turtles ADR to reach agreement as a team. This ADR should also specify the deprecation procedure for the existing controller.v3
clusters the default resource for importing CAPI clusters to Rancher.Child issues