Related backend rancher/rancher#47737 now in 2.12.0 so pushing this out of 2.11.0.

@richard-cox if you have the RFC link, let me know since I couldn't easily find it.

The description of the k3s-based-upgrader-uninstall-concurrency setting needs to be updated by removing the reference to "imported clusters" as this setting will now apply to both imported and node-driver clusters.

We should update to cover both types rather than remove one (to avoid confusion)

A new setting needs to be added to the list:

• Name: system-agent-upgrader-install-concurrency (default: 5)
• Description: Defines the maximum number of clusters in which Rancher can concurrently install the resources required for upgrading system-agent.

We should consider if this is something to show in the ui or not

Hi @richard-cox
'Defines the maximum number of clusters in which Rancher can concurrently uninstall the legacy rancher-k3s-upgrader or rancher-rke2-upgrader app from imported or node-driver K3s or RKE2 clusters.' Doesn't it sound a bit awkward? Maybe we should just change it to 'Defines the maximum number of clusters in which Rancher can concurrently uninstall the legacy rancher-k3s-upgrader or rancher-rke2-upgrader app from K3s or RKE2 clusters.' Because I don't think there is any other type of K3s or RKE2 cluster

The description of the k3s-based-upgrader-uninstall-concurrency setting needs to be updated by removing the reference to "imported clusters" as this setting will now apply to both imported and node-driver clusters.

We should update to cover both types rather than remove one (to avoid confusion)

^

There is also custom clusters, however not sure how they align with this feature. Otherwise we could mention "all" types