Bridging aMulti-CloudEnvironmentTim HockinGoogle Cloud
View Slide
AvailabilityLocalityRiskIsolationLegacyAcquisitionsMulti-Env
By 2021, over 75% of midsizeand large organizations will haveadopted a multi-cloud or hybridIT strategy**Gartner, Predicts 2019: Increasing Reliance on Cloud Computing Transforms ITand Business Practices, December 2018+75 %
Using multiple clouds meansyou are exposed to all of thedifferences between them● UI, API, CLI● Product capabilities● Identity, AuthCacophony
Differences between clouds rundeep, impact what you build,and how you operate● Networking● Storage● Autoscaling● App lifecycleExperience
The logical solution to variationsacross platforms is newabstractionsAbstraction
It’s very easy to accidentallydepend on facets of a specificenvironment and get stuckLock-In
Mastering one cloud is hard;mastering multiple clouds canbe overwhelmingTraining
You don’t want to train yourteams on multiple cloudsYou don’t want to tailor yourdeployments for each cloudConsistency
Look for abstractions that arewidely adopted and which aresupported by the underlyingprovidersStandard
Consistent, flexible CLI & APIAbstraction of infrastructureSingle dev / ops experienceHighly portable workloadsKubernetes
High-level enough to hide theworst differences betweencloudsLow-level enough to run almostanythingElevate
Build your custom platform on asolid foundation that abstractsthe infrastructurePlatform
Kubernetes is not an islandEcosystem
Numerous options and solutionsexist, and people are ready to fillin the gapsLeverage
There are no magic bulletsNo system is perfectAnyone who says otherwise isselling somethingReality Check
Kubernetes can be the threadthat ties multi-cloud solutionstogether, but it is not a solutionon its ownFuture