rancher-docs/versioned_docs/version-2.10/shared-files/_cluster-capabilities-table.md

Action	Rancher Launched Kubernetes Clusters	EKS, GKE and AKS Clusters1	Other Hosted Kubernetes Clusters	Non-EKS or GKE Imported Clusters	Turtles/CAPI Clusters
Using kubectl and a kubeconfig file to Access a Cluster	✓	✓	✓	✓	✓
Managing Cluster Members	✓	✓	✓	✓	✓
Editing and Upgrading Clusters	✓	✓	✓	✓2	✓5
Managing Nodes	✓	✓	✓	✓3	✓5
Managing Persistent Volumes and Storage Classes	✓	✓	✓	✓	✓
Managing Projects, Namespaces and Workloads	✓	✓	✓	✓	✓
Using App Catalogs	✓	✓	✓	✓	✓
Configuring Tools (Alerts, Notifiers, Monitoring, Logging, Istio)	✓	✓	✓	✓	✓
Running Security Scans	✓	✓	✓	✓	✓
Ability to rotate certificates	✓	✓
Ability to backup and restore Rancher-launched clusters	✓	✓		✓4
Cleaning Kubernetes components when clusters are no longer reachable from Rancher	✓

1. Registered EKS, GKE and AKS clusters have the same options available as EKS, GKE and AKS clusters created from the Rancher UI. The difference is that when a registered cluster is deleted from the Rancher UI, it is not destroyed.

2. For imported clusters, cluster configuration options can only be edited for K3s and RKE2 clusters.

3. For imported cluster nodes, the Rancher UI exposes the ability to cordon, drain, and edit the node.

4. For imported clusters using etcd as a control plane, snapshots must be taken manually outside of the Rancher UI to use for backup and recovery.

5. Exclusively via the Cluster API.