33 votes3 comments · Azure Kubernetes Service (AKS) » Integration with 3rd party tools and frameworks · Flag idea as inappropriate… · Admin →
34 votes2 comments · Azure Kubernetes Service (AKS) » Support for Kubernetes features · Flag idea as inappropriate… · Admin →
Kubernetes federation is not mature at this point. The v1 solution remains in an alpha state, with no path to GA. There is discussion around a V2 approach in sig-multicluster but it is still nascent. As a result, we have no near-term plans to enable it in AKS. If your goal is simply to run the same app across multiple clusters with traffic routing between them, you can mostly accomplish that with a good CI/CD pipeline and Azure Traffic Manager.
An error occurred while saving the commentTomas Maggio commented
What's the current train of thought around this today?
Federation v2 seems to be addressing the biggest problems when dealing with multiple clusters. CI/CD toolset can do so much before you run into scalability issues (multiple ctrl planes, resource utilization...).
You might (we do) want to have multiple cloud presence within the same regions (AWS and Azure within Sydney for example) but not necessarily having to manage them independently.
Not a silver bullet but it solves the immediate needs once you grow past playing with k8s.