Seamless Rancher + Turtles installation

[anmazzotti]

What would you like to be added (User Story)?

Currently, the Turtles installation process relies on Rancher being installed first.

All needed actions for Turtles to run in conjunction with Rancher are automated by the pre-install job, however uninstalling the Turtles chart still leaves the user with a manual step to restore the Rancher embedded-capi Feature.

This leads to confusion and possible errors during a setup of a new environment, for example when users try to install Rancher and Turtles in parallel, or installing Turtles before Rancher, or installing Turtles to experiment with it, to then uninstall it later.

Detailed Description

It would be easier for the end user to rely on Rancher installing the CAPI support (via Turtles) as a feature.
This way setting up a new cluster would ideally be a one action process.

This should work similarly as for other Rancher features, like Fleet.

This way it will also be easier to pin versions and ensure only compatible providers can run, depending on the Rancher version installed. Most important to ensure the CAPI version is still compatible with Rancher, when managed by Turtles, and avoid all potential scenarios where running Rancher in embedded-cluster-api: false mode may fail.
This may be especially important to ensure Turtles and Cattle provisioning can run in parallel without conflicts.

Having a chart installation controller will also help fully automating uninstall steps.

Bonus feature

A chart install controller may also take care of installing the appropriate Turtles UI extension, so that the user also does not have to install this manually.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature