[EPIC] ClusterClasses and GitOps lifecycle

[anmazzotti]

This issue collects a list of intended steps to:

• Consolidate all maintained ClusterClasses in one location
• Provide guidance and best practices to implement GitOps for ClusterClasses and Clusters lifecycle
• Provide a practical guide on how to integrate Fleet
• Improve the quick start experience to need the minimum amount of actions possible

Subtasks

• Remove all Cluster definitions (to prevent users from accidentally provision unwanted clusters when importing classes)
• (?). Publish templates as OCI artifact for centralized consumption
• (?). Implement test coverage on all published ClusterClasses
  • What happens on Cluster deletion? Is that going to be stuck, for example if the InfraTemplates or other resources are also deleted at the same time? (See: commit )
  • ClusterClasses versioning and updates. Is creating a new ClusterClass and referencing it to an existing Cluster going to work? (See: doc )
  • How to manage ClusterClasses lifecycle
  • How to manage Clusters lifecycle
  • How to integrate Cluster API Add-on Provider for Fleet (CAAPF) to customize managed Clusters (ClusterResourceSet alternative)
• Improve the quick start tutorial so that the only action needed is to consume an out-of-the-box ClusterClass (can have different tabs per infra provider).
• Archive https://github.com/rancher-sandbox/rancher-turtles-fleet-example

[salasberryfin]

From a conversation with UI, they're interested in having ClusterClass samples with as many configurable patches as possible trying to evaluate how we can give a UX similar to the existing one when using v2prov:

[alexander-demicev]

Closing in favor of smaller epics