An infrastructure administrator needs to optimize a Google Kubernetes Engine (GKE) Standard cluster to handle fluctuating workload demands while maintaining application availability during node upgrades. The workload requires custom node OS kernel parameters. Which TWO configurations must the administrator implement? (Select TWO)
- Enable the Cluster Autoscaler on the GKE node pool using gcloud container node-pools update with --enable-autoscaling, --min-nodes, and --max-nodes flags.Answer
- Specify CPU and memory resource requests in the Pod manifests and configure a Pod Disruption Budget (PDB) for the deployment.Answer
- CConfigure a Horizontal Pod Autoscaler (HPA) to automatically add or remove Compute Engine worker nodes when CPU utilization breaches target thresholds.
- DMigrate the cluster to GKE Autopilot mode to eliminate node management overhead while retaining custom node OS kernel configuration privileges.
Answer
The administrator must enable Cluster Autoscaler on the GKE node pool using gcloud container node-pools update, and specify Pod resource requests alongside a Pod Disruption Budget.
Enabling Cluster Autoscaler on the GKE node pool ensures worker nodes scale according to demand. Setting explicit Pod resource requests is required for Cluster Autoscaler to identify pending Pods, and establishing a Pod Disruption Budget guarantees workload availability during node updates. GKE Standard must be retained because custom node OS kernel tuning is disallowed in GKE Autopilot.
Step-by-Step Solution
Key Concept
Managing GKE Cluster Autoscaler, Pod Resource Requests, and Pod Disruption Budgets
Estimated Time:1m 30s