Hi everyone! I recently tried using Rancher (manager) to manage an AKS cluster and ran into a few problems, including the fact that Rancher doesnt support Cilium as a Network Policy. I realized that the Azure community seems almost non-existent (#C010UHEMYDT has 🦗 sounds 🎵 ). Anyone have insight as to why it seems Azure is marginally used with rancher employee ?

From my experience we do have many users/enterprise customers managing AKS via Rancher. Can you share what issues you faced ?

Yeah no supporting Cilium as NP would be a deal breaker for me. Here's all I unofficial found "Rancher Manager does natively support Cilium — support is much stronger for Rancher-provisioned RKE2 than for Rancher managing Azure-native AKS+Cilium."

Sorry for the delay; I shouldn't have posted something before taking some time off 😄 . Not only does it not support Cilium but it also requires enabling local accounts, which is explicitly discouraged by Microsoft. Also regarding the lack of support for Cilium, I created some pull requests (aks-operator and rancher) 3 weeks ago and haven't gotten any feedback since. @quick-accountant-97840 I would be curious to know how your customers manage AKS and their experience has been. From my limited use, it's already been a pain and I've encountered some blockers.