with-agents

Google Cloud Essentials — selected guide

Top 3 ways to run your containers on Google Cloud

Google Cloud Tech 4 of 8
Open original playlist (opens in a new tab)
In this collection Browse 8 summaries 4 of 8

An unnamed presenter compares GKE, Cloud Run, and Compute Engine by the infrastructure and orchestration control each exposes. [00:00:00]-[00:04:16]

Key Points Covered

  • Containers package an application with its dependencies, but the runtime determines how much infrastructure a team operates. [00:00:00]-[00:01:04]
  • GKE provides managed Kubernetes orchestration, scheduling, scaling, health, upgrades, and cluster options. [00:00:00]-[00:02:08]
  • Cloud Run provides a managed, scale-to-zero model for stateless containers, while Compute Engine supports containers on familiar virtual machines. [00:02:08]-[00:04:16]
  • The delivery path joins image storage, access control, automation, vulnerability information, and runtime deployment. [00:04:16]-[00:05:19]

The 2020 Anthos and Google Container Registry paths are historical: use current documentation for Artifact Registry, current GKE modes, Cloud Run capabilities, and present GKE/Cloud Run boundaries.

Full video: https://www.youtube.com/watch?v=jh0fPT-AWwM(opens in a new tab)