Bridging a Multi-Cloud Environment

Transcript

1. Bridging a Multi-Cloud Environment Tim Hockin Google Cloud

2. None

3. Availability Locality Risk Isolation Legacy Acquisitions Multi-Env

4. 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 %

5. Using multiple clouds means you are exposed to all of

   the differences between them • UI, API, CLI • Product capabilities • Identity, Auth Cacophony

6. Differences between clouds run deep, impact what you build, and

   how you operate • Networking • Storage • Autoscaling • App lifecycle Experience

7. The logical solution to variations across platforms is new abstractions

   Abstraction

8. It’s very easy to accidentally depend on facets of a

   specific environment and get stuck Lock-In

9. Mastering one cloud is hard; mastering multiple clouds can be

   overwhelming Training

10. You don’t want to train your teams on multiple clouds

    You don’t want to tailor your deployments for each cloud Consistency

11. Look for abstractions that are widely adopted and which are

    supported by the underlying providers Standard

12. Consistent, flexible CLI & API Abstraction of infrastructure Single dev

    / ops experience Highly portable workloads Kubernetes

13. High-level enough to hide the worst differences between clouds Low-level

    enough to run almost anything Elevate

14. Build your custom platform on a solid foundation that abstracts

    the infrastructure Platform

15. Kubernetes is not an island Ecosystem

16. Numerous options and solutions exist, and people are ready to

    fill in the gaps Leverage

17. There are no magic bullets No system is perfect Anyone

    who says otherwise is selling something Reality Check

18. Kubernetes can be the thread that ties multi-cloud solutions together,

    but it is not a solution on its own Future
19. None