This message was deleted.
# general
a
This message was deleted.
🙌 1
a
Entries pertaining to individual control plane nodes imply that cluster was created with
authorised cluster
endpoint
enabled
a
Ohh, I read about that, so I should enable that somehow
Can you enable it for a cluster after import?
a
If you're running 2.6.3 or newer, yeah https://github.com/rancher/rancher/issues/35161
Or if it's provisioned by rancher you can edit the cluster and go to network I believe. There's a checkbox for ace
a
Nah, I'm dealing with AKS clusters and CAPI/CAPV clusters
a
Oh non rke/k3s clusters?
Then no, iirc
For AKS it depends on its settings
a
Thanks for all the info, helps me quite a bit. Now we have a well defined challenge to overcome 🙂
a
Also. Did you import AKS as a generic cluster or a native aks cluster?
a
Looks like they were done as a generic cluster; but that's something we can still change obviously
Do native AKS clusters understand paused clusters (to save cloud-costs) better than generic clusters?