Validate Cluster Management View of standalone Turtles cluster

[richard-cox]

• It's still expected for users to create clusters outside of the UI via native CAPI resources + rancher turtles
• We should confirm that they are fine to view in cluster management
  • machines list shows correct data
  • cluster actions work fine
• Lists like More Resources --> Machine / MachineSet / MachineDeployments should continue to group by cluster (not sure this is applicable)

The assumption is that this is all still fine, but would like to confirm just in case

[richard-cox]

@mantis-toboggan-md wasn't sure which label to add for this, do we shunt all things provisioning into area/clusterprovisioningv2?

[mantis-toboggan-md]

I'm not opposed to using that as a catch-all, I think anything tracked under provisioning in the project board is fine. capi clusters created outside rancher and imported with turtles were treated as generic imported clusters last I checked so I added that label here. I've also created a new area/capi label

[mantis-toboggan-md]

I created an aws/kubeadm cluster from the turtles example, including auto-import label to import it into Rancher.

• editing imported CAPI clusters shows the imported cluster config -- not sure we want this? Maybe editing the capi cluster yaml would be more accurate? idk
• kubectl shell, download kubeconfig work as expected
• cluster management list view shows accurate information
• detail page aligns with other generic imported clusters
• machines list looks accurate and groups by cluster
  -cluster explorer works

[richard-cox]

i think we keep that edit experience the same, however in cluster management expose the resource types they need to manage via yaml.

Would you be able to create a list of the resource types required to manage the following types of clusters?

• native capi via turtles
• v2prov capi

We can then together organise and stick in group/s in the cluster management side bar

We should exclude anything provider specific (ui extension's catering for cpai providers should now, with the new product api, add their types to the same groups-ish)