Your company hosts a microservices workload on a Google Kubernetes Engine (GKE) cluster. During high traffic spikes, CPU consumption increases significantly across existing pods, resulting in high response latency. The existing cluster nodes have adequate spare CPU and memory resources to handle additional pod workloads. You need to configure automated scaling so that new pod replicas are scheduled when CPU utilization reaches a high threshold. What operational action should you take?
- Configure a Horizontal Pod Autoscaler (HPA) targeting the Deployment using the kubectl autoscale command.Cevap
- BEnable Cluster Autoscaler on the GKE cluster node pool using the gcloud container node-pools update command with the --enable-autoscaling flag.
- CMigrate the existing cluster from GKE Standard mode to GKE Autopilot mode using gcloud container clusters update.
- DRecreate the GKE node pool using Spot VMs by providing the --spot flag in the gcloud container node-pools create command.
Cevap
Configure a Horizontal Pod Autoscaler (HPA) targeting the Deployment using the kubectl autoscale command.
Configuring a Horizontal Pod Autoscaler (HPA) using kubectl autoscale dynamically adjusts the number of pod replicas based on CPU utilization. Because the cluster nodes already possess adequate CPU and memory capacity, adding pod replicas effectively distributes the load without needing to scale node pool infrastructure.
Adım Adım Çözüm
Anahtar Kavram
Managing GKE Workload Autoscaling with Horizontal Pod Autoscaler (HPA)
Tahmini Süre:1m 30s