Display management.v3 clusters in dashboard, without provisioning cluster

[Danil-Grigorev]

Is your feature request related to a problem? Please describe.

Import of a cluster can be performed using management.v3 cluster resource. The cluster is successfully imported, however it is not displayed in UI.

Manually accessing cluster explore via https://${rancher-url}/dashboard/c/${mgmt-cluster}/explorer shows the dashboard, as expected.

Describe the solution you'd like

View and explore management clusters without provisioning clusters.

Describe alternatives you've considered

Extend /dashboard/c/_/manager/management.cattle.io.cluster with similar information to home page, including explore option.

Additional context

[Danil-Grigorev]

Fixing this issue can help resolving rancher/turtles#622, since disabling creation of provisioningv1 cluster prevents installation of the fleet agent on the imported cluster, allowing for more granular configuration options, and alternative installation paths, such as http://github.com/rancher-sandbox/cluster-api-addon-provider-fleet

Otherwise the cluster explore functionality is fully functional (with exceptions of the native fleet installation), user can request kubeconfig, install apps or view the resources.

This issue came from investigation, following the discussion in https://suse.slack.com/archives/C04UQMP0FPB/p1723563705780859

[nwmac]

@Danil-Grigorev I don't think we can easily do this from the UI side as we rely heavily on the prov cluster - our understanding from previous conversations with backend was that this was the go-forward resource to be used for a cluster and that there would always be a provisioning cluster for every cluster.

I understood that the Rancher backend has a sync process that ensures that there is always 1-1 mgmt and prov cluster that are kept in sync.

I think we need to be clear about the role of the two resources, why we have two, why we can have one and not the other (both ways around) and we need to ensure everyone understands that before we update the UI.

I don't think we should remove the prov cluster as a way to prevent fleet agent installation and other configuration - I'd suggest you consider adding an annotation or field to the prov cluster to indicate to Rancher that it should NOT install those components and that Rancher should use that annotation of field.