Google introduced Anthos as a hybrid and multi-cloud platform built around Google Kubernetes Engine (GKE) and open-source Kubernetes. The goal was to let organizations run and manage containerized applications consistently across Google Cloud and on-premises environments, with plans to extend to other clouds.
Soon after the announcement, Google stated that Anthos’ hybrid functionality was generally available on Google Cloud and in customer data centers via GKE On-Prem. This established Anthos as a production platform for running the same Kubernetes-based approach in both cloud and on-prem environments.
Anthos Config Management (now commonly referenced through Config Sync documentation) became generally available, enabling teams to manage Kubernetes configuration from a Git repository. This supported a “GitOps” workflow, where Git is treated as the source of truth for cluster configuration.
Google’s release notes show Anthos 1.0 becoming available in mid-2019, formalizing a versioned release cadence. This mattered because customers could plan upgrades and align Anthos components with supported versions over time.
Google shipped Anthos 1.1, continuing a steady release pattern with updates across multiple components (such as config management and service mesh). This period reflected Anthos’ shift from initial launch into ongoing operational maturity through frequent patch and minor releases.
Anthos Service Mesh became generally available, providing a supported service mesh layer based on Istio. A service mesh helps manage service-to-service traffic, security (like encryption), and observability (like tracing) for microservices running on Kubernetes.
Google made Anthos generally available for AWS, moving beyond Google Cloud and on-premises into a major third-party public cloud. This marked a key step toward Anthos’ multi-cloud promise: a consistent Kubernetes platform and management approach across providers.
Google made Anthos on bare metal generally available, letting customers run Anthos on physical servers without requiring a hypervisor layer. This expanded hybrid options for organizations that needed Kubernetes on existing hardware or specialized on-prem environments.
Google’s “managed control plane” option for its service mesh reached general availability, reducing the operational work required to run a service mesh. This was important for hybrid and multi-cloud environments, where operating identical control-plane software across many clusters can be complex.
Anthos on Azure became generally available through Google’s Multi-Cloud API, enabling lifecycle management of Anthos clusters running in Azure. This advanced Anthos from “multi-cloud in principle” to a more complete multi-cloud footprint across major hyperscalers.
Google released a new generation of “Anthos attached clusters,” strengthening support for connecting existing Amazon EKS and Azure AKS clusters to Google’s management plane. This mattered because many organizations already had Kubernetes in other clouds and wanted centralized visibility and policy management without rebuilding clusters.
At Google Cloud Next 2023, Google introduced GKE Enterprise as an enterprise Kubernetes platform that builds on earlier work in Anthos and GKE. This represented a shift toward packaging Anthos’ multi-cluster, hybrid, and multi-cloud capabilities into a more unified “enterprise” Kubernetes offering.
Google expanded attached clusters to support attaching any CNCF-conformant Kubernetes cluster (beyond just EKS and AKS). This broadened Anthos’ multi-cloud and hybrid reach by recognizing that real-world environments often include multiple Kubernetes distributions.
Google announced GKE Enterprise would be generally available on November 15, 2023, positioning it as the next evolution of its container platform portfolio. As a storyline endpoint, this GA milestone reflects how the 2019–2023 Anthos era matured into a consolidated, enterprise-focused hybrid and multi-cloud Kubernetes platform.
Google Anthos: development, releases, and multi-cloud deployments (2019–2023)