Regarding the other questions you mention. Some comments: • 2.7.1 is already live and 2.7.2 will be released soon (in April) • You are never left alone. All the ecosystem tries to follow the Kubernetes release cycle and so do we. You can be sure that when AKS supports 1.25 there'll be a Rancher version that will support 1.25. • 2.7.2 (this month) will bring support for k8s 1.25 • The AKS integration is bidirectional. Any change done with Rancher to the AKS configs, size, k8s version.0.. will be automatically visible on your Azure console and vice versa.

• Yes, you can remove clusters from Rancher Management and add the back later on. • You should not be worried. As I explained AKS support for 1.25 and Rancher support for 1.25 may not happen exactly the same day but should always happen within a reasonable timeframe. • There are no differences between imported AKS clusters and Rancher deployed AKS clusters. Rancher uses the Azure API. You can also import and AKS cluster as a generic cluster but I can't think of any reason to do that (there are no benefits and you loose the value of being able not to just deploy and manage workloads but also changing configs, add/remove nodes, ...)