I am experiencing some weird behaviours trying to run Rancher.
This is the situation:
• 1.24.9 RKE2 Cluster (1 Master + 2 Nodes)
• Context is Airgap (no internet access)
• Cert-manager installed through Helm Chart
• Rancher 2.7.1 installing though Helm Chart
When launching the install of Rancher, it seems to fail looking for the following file /home/aks-operator/.kube/config and failing to list and watch *v1.AKSClusterConfig (get aksclusterconfigs.meta.k8s.io).
The issue is, I am not using AKS… Is there a Chart var or Env var with which I could specify that it is running on an RKE2 cluster ?
02/28/2023, 3:55 PM
normally AKS operator is when you have an imported cluster in Rancher from AKS.