Anthos support for multi-cloud is generally available
Disclaimer: I work at Google Cloud, helping &quot;developers&quot; understand what Anthos is.<p>(If you criticize my comment, there&#x27;s a decent change the marketing is gonna have a discussion with my boss about my employment. I&#x27;ll try not to use as many marketing-y terms as the article.)<p>At a high level, if you&#x27;re a solo developer or a small company, you probably don&#x27;t need to understand everything going on there, many Anthos features&#x2F;products are actually available a la carte, possibly under different names.<p>First, I’ll agree that the blog post is written in a way that might be hard to grasp for hands-on practitioners (assuming I know HN enough, since I visit it 30 times a day). I&#x27;ll start with an architecture diagram: <a href="https:&#x2F;&#x2F;cloud.google.com&#x2F;anthos&#x2F;docs&#x2F;concepts&#x2F;overview" rel="nofollow">https:&#x2F;&#x2F;cloud.google.com&#x2F;anthos&#x2F;docs&#x2F;concepts&#x2F;overview</a><p>You might still find this diagram difficult to understand (unless you live with the &quot;cloud-native&quot; stuff day to day) so I&#x27;ll break this down for you:<p>- Anthos GKE: This is basically the GKE (Google Kubernetes Engine) you know. But it is now capable of running clusters not just on Google Cloud. If you ever thought &quot;ahh, X cloud doesn&#x27;t have good Kubernetes support&quot;, well Google can bring GKE quality to that cloud (AWS support is now GA, Azure is in preview) or to your on-prem datacenter, or AWS&#x2F;Azure account. The GKE you know is still available with pay-as-you-go model.<p>I must note that this GKE on-prem&#x2F;hybrid capabilities are probably the most critical part of Anthos stack.<p>- Anthos Service Mesh: This is Istio (the open source service mesh), set up and managed for you. It helps you (1) connect your services, even if they&#x27;re across different datacenters or clouds (2) automatically export telemetry like traces, metrics and set up SLOs&#x2F;alerts with them (3) set policies for your RPC traffic at high level e.g. tcp retry policies should be like  X (4) enable mTLS automatically without changing your code across ALL your fleet and without having to run a PKI. (If you&#x27;re still not convinced about service mesh, you probably don&#x27;t have a RPC-heavy infra like some companies, maybe you don&#x27;t need it.) You can technically install&#x2F;manage Istio yourself across your clusters, but with Anthos, Google does that for you.<p>- Cloud Run for Anthos: This is actually hosted Knative (open source serverless stack on Kubernetes) for you. If you like rapid request-based autoscaling containers, you can have it anywhere (GCP, AWS, on-prem). You can install Knative anywhere, but Google does it for you and ensures it works properly with Istio and Kubernetes versions. I&#x27;ve written a blog post explaining what Knative does here: <a href="https:&#x2F;&#x2F;ahmet.im&#x2F;blog&#x2F;knative-better-kubernetes-networking&#x2F;" rel="nofollow">https:&#x2F;&#x2F;ahmet.im&#x2F;blog&#x2F;knative-better-kubernetes-networking&#x2F;</a> Basically, this works like a CaaS (containers as a service)  or build your own opinionated in-house opinionated PaaS with this.<p>We also offer Cloud Run as a fully-managed serverless product (not running on GKE, runs on Google’s infra directly) if you&#x27;re into that: <a href="https:&#x2F;&#x2F;cloud.run&#x2F;" rel="nofollow">https:&#x2F;&#x2F;cloud.run&#x2F;</a><p>- Anthos Config Management: This is available to GKE users as &quot;GKE Config Sync&quot;. It&#x27;s basically a GitOps tool (though not a complete suite like some stuff like Weaveworks Flux etc). You point it to a git repo&#x2F;branch, and it will go create Kubernetes manifests in that directory across your clusters. It has a pretty neat model where leaf directories correspond to Kubernetes namespace and there&#x27;s inheritance to fanout Kubernetes policy objects to multiple namespaces etc. AFAIK many companies using Kubernetes at scale build similar in-house solutions to this. So we worked with them to create a solution for everyone. This product also has some policy enforcement features and monitoring to see if your Kubernetes objects are propagating properly to your clusters.<p>- Other components: You&#x27;ll find them on the page I linked. I think they are not as interesting to the day to day practitioners here.<p>Obviously I&#x27;ve oversimplified many of these, but the docs of each specific product do a decent job explaining, you should read if you&#x27;re interested.<p>I&#x27;d say that if you are a practitioner, you don&#x27;t need to worry much about details of Anthos. You can continue focus on the technologies you need to know (choose how low-level you wanna go: containers, Kubernetes, RPC or networking layer&#x2F;service mesh, DevOps&#x2F;GitOps) and continue to be successful.<p>However, if you work at a company which doesn&#x27;t haven&#x27;t gone through the cloud native application modernization (I&#x27;m hitting my head on the wall for you for saying this), Anthos can actually help your company use cloud-native stack WITHOUT having to go to cloud.<p>As you might imagine, a ton of companies out there are (perhaps happily) run on infrastructure stacks from another time. However, those looking to change it and try to use Kubernetes, they need to build a lot of in-house tooling, hire talent to manage Kubernetes. Google is decent (maybe more) at running Kubernetes clusters at scale for many customers, so Google can bring this service and all the listed above to you.<p>I&#x27;m not that familiar with pricing, though as you can see from <a href="https:&#x2F;&#x2F;cloud.google.com&#x2F;anthos&#x2F;pricing" rel="nofollow">https:&#x2F;&#x2F;cloud.google.com&#x2F;anthos&#x2F;pricing</a> if you want to use these features on just on GCP, there&#x27;s a $30 vCPU&#x2F;month cost based on GKE nodes you&#x27;re running. For other stuff, you need to contact support.<p>I should probably make this a blog post.