Google Associate Cloud EngineerPlanning and configuring a cloud solutionMedium
A development team is building a new microservices-based application using containers. Each microservice will have varying resource requirements and traffic patterns. The team wants to focus on writing code and minimize operational overhead for managing the underlying Kubernetes infrastructure, including node provisioning, scaling, and upgrades. Which Google Kubernetes Engine (GKE) mode should they choose?
- AGKE Enterprise
- BGKE Standard
- CGKE Autopilot
- DGKE on Bare Metal
Show answer & explanationAnswer & explanation
Correct answer: C. GKE Autopilot
GKE Autopilot is a fully managed GKE mode where Google automatically manages the cluster's underlying infrastructure, including nodes, scaling, and upgrades. This allows developers to focus entirely on their applications without needing to manage the Kubernetes control plane or nodes.
Why the other options are wrong
- A. GKE Enterprise is a bundle of features for enterprise-grade GKE use, but 'Autopilot' is the specific mode that addresses the operational overhead of node management.
- B. GKE Standard requires manual management of node pools, scaling, and upgrades, increasing operational overhead.
- D. GKE on Bare Metal is for running GKE on on-premises hardware, not for minimizing operational overhead in Google Cloud.
GKE Autopilot
A fully managed operational mode for Google Kubernetes Engine (GKE) where Google automatically manages the cluster's underlying infrastructure, including node provisioning, scaling, and upgrades.
- Fully managed Kubernetes nodes
- Pay-per-pod model
- Automatic scaling and upgrades
- Focus on application development, not infrastructure management
- Enhanced security defaults
Memory trick: Autopilot drives itself; Standard needs a co-pilot.