The document discusses a Google Developers Group event held in San Diego on August 10, 2021, featuring a senior DevOps engineer who is passionate about Kubernetes and CI/CD. It highlights the advantages of Google Kubernetes Engine (GKE) over Google Compute Engine (GCE), particularly focusing on autoscaling, self-healing, and configuration as code. The document concludes with an acknowledgment of the operational challenges and limitations of GKE's autoscaling capabilities.

1. San Diego Google Developers Group - August 10, 2021 https://gdg.community.dev/gdg-san-diego/

2. ● Senior DevOps Engineer
● Guitar Player
● Beer Drinker
● Dad
● Lover of Kubernetes, CI/CD and Developer Happiness
● Golang Enthusiast
● Noted Sports Fan
● Obsesses over BBQ and Smoking Meat
Who is this guy?

3. What’s the Deal?
● Why not just use GCE (Google Compute Instances)?
● What problems does GKE solve that GCE doesn’t?
● Autoscaling...and other “problems” GKE introduces...and solves!

4. DISCLAIMER

5. Developer Confidence...it’s the
name of the game

6. GCE GKE
● Autoscaling
● Self-healing
● Configuration as Code?
● Cost
● Autoscaling
● Self-healing
● Configuration as Code
● Cost
● Clean Build Environment Every Build
● Time to Autoscale
● Build Time Affect
● Operations

8. Problem: GKE Autoscaling is too good

9. Autoscaling...but only up

10. It works 60% of the time….every time

11. Questions?
Q&A