Containers for Google Clouds
Google Kubernetes Engine, or GKE, is Google's managed Kubernetes service for running containerised applications across a cluster of machines. It handles control plane upgrades and node management so you can focus on deployments, services and scaling. In this roadmap it follows compute, building on container basics for larger multi-service systems.
Stage: Compute · Part of the Google Cloud roadmap · Last reviewed 19 November 2026
What to learn in Containers
- Create a GKE cluster and fetch credentials with gcloud and kubectl
- Deploy a workload using a Deployment manifest and expose it with a Service
- Explain the difference between Autopilot and Standard cluster modes
- Scale a deployment manually and with a horizontal pod autoscaler
- Push an image to Artifact Registry and pull it from the cluster
Containers interview questions
What is the difference between GKE Autopilot and Standard mode?
In Standard mode you configure and manage node pools yourself and pay for the nodes. In Autopilot, Google manages nodes and you pay based on the resources your pods request. Autopilot reduces operations work but applies more restrictions on what workloads can do.
How does a Kubernetes Service differ from a Deployment?
A Deployment describes the desired pods and handles rollouts and replicas. A Service gives those pods a stable network address and load balances traffic to them, because individual pod IPs change whenever pods are replaced.
Where Containers fits in the Google Cloud roadmap
Containers belongs to the Compute stage (intermediate level). Run apps.
Other units in this stage
Back to the full Google Cloud roadmap