Google Cloud Essentials — selected guide
Top 3 ways to run your containers on Google Cloud
Eight concise orientations to compute, storage, containers, projects, delivery, logs, and errors
Eight 2020–2022 explainers introduce compute, storage, containers, Firebase projects, build tools, logging, and error reporting through the workloads each service supports.
Google Cloud Tech 4 of 8
In this collection Browse 8 summaries 4 of 8
Containers package an application and its dependencies, but someone still has to run and scale them. This 2020 overview compares Google Kubernetes Engine (GKE), Cloud Run, and Compute Engine by how much of that infrastructure a team controls. 00:00–04:16(opens in a new tab)
Key Points Covered
- GKE coordinates containers across a cluster. Kubernetes schedules and scales containers and tracks their health. The overview shows controls for machine types and locations, with managed features for node repair and upgrades. 00:00–02:08(opens in a new tab)
- Cloud Run removes cluster setup. The example deploys a stateless container by selecting a location, name, and authentication requirements. The platform manages scaling, including scaling to zero when idle. 02:08–03:12(opens in a new tab)
- Compute Engine keeps a VM-based workflow. Containers run on virtual machines, allowing teams to retain familiar tools. The example uses Container-Optimized OS, a smaller operating system with a preinstalled container runtime; managed instance groups can add scaling and rolling updates across VMs. 03:12–04:16(opens in a new tab)
Full video: https://www.youtube.com/watch?v=jh0fPT-AWwM(opens in a new tab)