Google Anthos: Hybrid Cloud on Your Infrastructure – ITPro Today Blog by Eric Slack

By Eric Slack, Monday, April 6th 2020

Analyst Blogs

This second in a series of articles, on making hybrid cloud a reality, looks at Google Anthos, how it works, the deployment options, how it compares with AWS Outposts and who should consider it. Read the first installment here

The public cloud has always been appealing, with the scale, flexibility and ease of use it offers. But issues with bandwidth, privacy and especially, cost, have made the hybrid cloud the preferred architecture for most companies. This combination of on-prem infrastructure and connectivity to the public cloud has promised to deliver many of the original benefits of the public cloud while adding container support for technologies like cloud-native development and CI/CD.

Most of the infrastructure vendors see the hybrid cloud as the public cloud extension to their on-prem offerings;  but the public cloud vendors are taking a different approach. One could argue these companies see the hybrid cloud as a way to replace traditional IT infrastructure altogether. In this blog series we’re looking at these new hybrid cloud options, AWS Outposts, Google Anthos and Microsoft Azure Stack, plus other solutions as they become available.


Google Anthos is an on-premises platform for running Kubernetes (K8S)-based applications on Google’s Kubernetes Engine (GKE) that connects to the Google Cloud Platform (GCP) in Google’s public cloud. Instead of providing the entire hardware and software stack as a service, Anthos leverages infrastructure partners to deliver their hybrid cloud experience.

Anthos runs on VMware, requiring four VMs in the initial configuration for administration, plus one to three VMs for each user cluster (to run workloads). Each VM must have 4 vCPUs, 8GB of memory and 40GB of storage space. Anthos requires layer 4 load balancers as well. The connectivity options are Cloud VPN, or a dedicated or partner interconnect.

Setting up Anthos in the data center requires an Anthos subscription (on-prem license) plus an active Google Cloud Project, essentially a GCP account that gives you access to APIs and sets up billing. Although the Anthos on-premises price is not listed on the current price page, at introduction in April 2019, prices were $100 per vCPU per month, sold in blocks of 100 vCPUs. Subscription prices for GCP are also not listed, but an on-demand price of $30 per vCPU per month for is scheduled to take effect in July. This puts a 100 vCPU deployment at $13,000 a month, plus support.

Anthos can also be run in third-party clouds, like AWS or Azure. While this does provide a little more flexibility by giving you a choice of public clouds, Google is still managing it.

Customers can use any appropriate hardware (that meets VMware vSphere’s requirements) or buy a solution from Google’s partners. Anthos Platform partners include HCI vendors Cisco HyperFlex, HPE SimpliVity, Nutanix, Dell EMC VxFlex or Intel. In addition, Google has established the Anthos Ready Storage program for storage vendors, currently including Dell EMC, HPE, NetApp, Portworx, Pure Storage and Robinio. These storage systems can be used to provide Persistent Volume Storage for Kubernetes clusters through a CSI plugin.

Containers and Microservices

Microservices are part of the appeal of container-based software development. In a microservices-based architecture, the communication between services is key. A service mesh is a dedicated infrastructure layer built into the application that manages this communication, instead of coding this into each service. This involves proxies running alongside each service as “sidecars”, providing metrics on operations, diagnosing problems and enhancing network security and reliability. Anthos Service Mesh includes a distribution of Istio, an open-source service mesh platform that’s available as an add-in.

Anthos runs in VMware, which means you can also run legacy VM-based workloads on the same cluster as your Anthos Kubernetes workloads. This makes Anthos more flexible for companies to adopt containers at their own pace, while still running applications in VMs. But to be clear, this isn’t the only turnkey solution for running containers and VMs in a hybrid cloud environment. VMware’s vSphere 7, Nutanix’s Karbon and Cisco’s HyperFlex Application Platform also support Kubernetes and VMs in the same platform; Nutanix on their AHV hypervisor and Cisco HXAP on KVM.

As we saw in the last blog, AWS Outposts is one way to bring the public cloud into your data center; Anthos is another. Both create a hybrid cloud infrastructure with a tight integration to the public cloud. Both set up a container-based compute environment for cloud-native development. Both give you access to their services “marketplace” and let you manage the whole thing from a single pane of glass. Aside from that, these are two very different approaches to creating a hybrid cloud.

Outposts is a 100% as-a-service experience, with AWS owning everything, installing it on site and managing it for you. With Anthos, you have to assume the configuration, acquisition and deployment duties, as well as on-going maintenance of the infrastructure. But you can choose the hardware since Anthos on-prem runs on any hardware stack that supports VMware – even existing infrastructure. This includes HCI clusters or servers with DAS or network-attached storage systems.

After it’s up and running Anthos brings a little piece of Google’s cloud into your data center. For companies committed to Google and want a hybrid cloud with the flexibility to choose the hardware Anthos may be a good option. For those that need a kubernetes-based solution on-prem, but aren’t “all-in” with Google’s cloud, another platform may be better.

Forgot your password? Reset it here.