Bridging a Multi-Cloud Environment Tim Hockin Google Cloud

No content

Availability Locality Risk Isolation Legacy Acquisitions Multi-Env

By 2021, over 75% of midsize and large organizations will have adopted a multi-cloud or hybrid IT strategy* *Gartner, Predicts 2019: Increasing Reliance on Cloud Computing Transforms IT and Business Practices, December 2018 +75 %

Using multiple clouds means you are exposed to all of the differences between them ● UI, API, CLI ● Product capabilities ● Identity, Auth Cacophony

Differences between clouds run deep, impact what you build, and how you operate ● Networking ● Storage ● Autoscaling ● App lifecycle Experience

The logical solution to variations across platforms is new abstractions Abstraction

It’s very easy to accidentally depend on facets of a specific environment and get stuck Lock-In

Mastering one cloud is hard; mastering multiple clouds can be overwhelming Training

You don’t want to train your teams on multiple clouds You don’t want to tailor your deployments for each cloud Consistency

Look for abstractions that are widely adopted and which are supported by the underlying providers Standard

Consistent, flexible CLI & API Abstraction of infrastructure Single dev / ops experience Highly portable workloads Kubernetes

High-level enough to hide the worst differences between clouds Low-level enough to run almost anything Elevate

Build your custom platform on a solid foundation that abstracts the infrastructure Platform

Kubernetes is not an island Ecosystem

Numerous options and solutions exist, and people are ready to fill in the gaps Leverage

There are no magic bullets No system is perfect Anyone who says otherwise is selling something Reality Check

Kubernetes can be the thread that ties multi-cloud solutions together, but it is not a solution on its own Future

No content