A digital publishing firm plans to migrate its containerized backend microservices to Google Kubernetes Engine (GKE). The microservices are stateless, follow standard Kubernetes configurations, and do not require custom host OS kernel modifications or privileged containers. The engineering team wants to minimize cluster administration overhead by transferring node provisioning, maintenance, and security patching responsibilities to Google Cloud, while paying only for the CPU, memory, and storage requested by running pods. Which GKE cluster architecture should the team deploy to meet these requirements?
- Deploy a GKE Autopilot cluster.Cevap
- BDeploy a GKE Standard cluster with Cluster Autoscaler enabled across all node pools.
- CDeploy a GKE Standard cluster utilizing Spot VM node pools for all workload deployments.
- DDeploy a GKE Standard zonal cluster with node auto-provisioning and manual node upgrades.
Cevap
Deploying a GKE Autopilot cluster satisfies the requirement for zero node management overhead and per-pod resource billing.
Deploying a GKE Autopilot cluster is the optimal architecture when an organization wants to minimize operational overhead. In Autopilot mode, Google Cloud provisions, secures, and manages the underlying worker nodes, node pools, and OS patches. Furthermore, billing in Autopilot mode is calculated per pod based on requested CPU, memory, and storage resource limits rather than total node compute capacity.
Adım Adım Çözüm
Anahtar Kavram
GKE Autopilot operational boundary and billing model