Fleet, Arc, sovereign clouds, and the edge-first world of 2030
This article is the last part of the Azure Kubernetes Chronicles: Multi-Cluster Edition.
Read the series introduction here.
Examining today’s multi-cluster landscape, it is tempting to focus solely on the pain points: identity fragmentation, policy drift, networking complexity, and monitoring silos. But the story does not end there. Kubernetes itself has evolved from a single-cluster dream to a multi-cluster necessity, and the governance ecosystem around it is growing just as quickly. To understand where things are headed, we have to look beyond today’s tools and into the future that is already taking shape.
Kubernetes was first released by Google in 2014 as an open-source system for orchestrating containers within a single cluster, providing scheduling, scaling, and workload management across a unified infrastructure. By around 2016–2018, as enterprise adoption accelerated, organizations began running multiple clusters to achieve regional availability, meet compliance needs, and support scalability, which introduced new challenges in networking, identity, and governance across environments. From 2019 onward, the landscape shifted further with the rise of hybrid and multi-cloud strategies, where clusters were deployed not only in private data centers but also across public clouds such as Azure Kubernetes Service, Amazon EKS, and Google GKE, as well as at the edge with lightweight distributions like k3s. Today, in 2025, Kubernetes has matured into a multi-cluster, multi-platform ecosystem, where interoperability and governance layers, such as Azure Arc, Anthos, and Fleet, enable enterprises to manage fragmented environments as a cohesive and unified platform.
The first and most obvious trajectory is the convergence of Fleet and Arc. Today, Fleet provides strong governance inside Azure, while Arc extends Azure’s control plane to clusters outside of it. But enterprises want more than two separate tools. They want a single experience that spans both. It is not hard to imagine Microsoft moving in this direction, Fleet handling workload placement and resource propagation across AKS, Arc extending governance and security across EKS, GKE, and the edge. Together, they could form the unified multi-cluster platform that enterprises have been waiting for.
At the same time, the European conversation around digital sovereignty is gaining momentum. Initiatives like GAIA-X, along with sovereign providers such as OVHcloud and Deutsche Telekom, are becoming part of enterprise strategies. The goal is not to abandon hyperscalers, but to prove independence from them. In this landscape, enterprises may find themselves running AKS in Amsterdam, EKS in Frankfurt, and a GAIA-X-aligned cluster in Paris, all of which will need to be governed as a whole. The pressure will grow for platforms like Arc or Anthos to integrate sovereign clouds alongside global ones, ensuring that sovereignty does not lead to fragmentation.
Is OVHcloud a viable option because of its presence in the United States?
OVHcloud is headquartered in France and positions itself as a European sovereign cloud provider, emphasizing EU data residency and certifications such as SecNumCloud. While the U.S. CLOUD Act allows American authorities to compel U.S.-based providers to hand over data stored abroad, OVHcloud argues that only its U.S. subsidiary, OVH US, falls under that law. The European entity (OVHcloud in the EU) operates separately and is not subject to U.S. jurisdiction, meaning that data stored and processed entirely within its European infrastructure remains governed solely by European law. In practice, OVHcloud is a viable option for a European sovereign cloud, provided customers contract with and use only its European services and avoid any ties to its U.S. operations.
The edge explosion is the third force reshaping the future. Analysts predict that by 2030, the majority of enterprise data will be processed outside of traditional data centers. That means retail stores with their own Kubernetes clusters, factories running predictive maintenance models locally, hospitals analyzing imaging on-site, and telecom towers hosting thousands of micro data centers. Edge will not replace cloud, but it will outnumber it. Instead of managing a handful of hyperscale clusters, enterprises will be managing hundreds or thousands of small, distributed ones. Governance platforms will need to scale in a new way, not just deeper into Azure and AWS, but wider across thousands of edge locations.
Finally, compliance itself will evolve. Instead of being an afterthought, regulations such as GDPR, NIS2, and DORA will be baked into platforms from the start. Enterprises will no longer bolt on compliance tools; instead, they will adopt predefined blueprints, hardened configurations, and automated audits. The future of Kubernetes governance will shift from proving compliance after the fact to operating within compliance by design.
Taken together, these trends indicate a world where multi-cluster Kubernetes is not just the norm, but a foundational aspect. Fleet and Arc will merge into something greater. Sovereign clouds will become part of everyday enterprise architecture. Edge will redefine the scale and distribution of clusters. And compliance will shift from an obstacle to an embedded feature of the platform.
Multi-cluster is no longer the messy truth of today. It is the strategic architecture of tomorrow. Enterprises that embrace this reality will not only survive regulatory and operational pressure but also position themselves for innovation in a world where cloud and edge are inseparable.
Previous: Azure Kubernetes Chronicles 11: Governing the Chaos