Your team has deployed a microservices application on Google Kubernetes Engine (GKE). You notice that one service has high latency during peak hours. The service is CPU-bound and uses a HorizontalPodAutoscaler (HPA) based on CPU utilization. What is the most likely cause of the latency?
Trap 1: The GKE cluster uses preemptible nodes that are frequently…
Preemptible nodes cause pod evictions, not gradual latency increase.
Trap 2: The service uses a global external HTTP(S) load balancer with…
Session affinity does not cause latency; it routes requests to the same backend.
Trap 3: The application does not implement request autoscaling at the…
Request autoscaling is not a built-in GKE concept.
- A
The GKE cluster uses preemptible nodes that are frequently reclaimed.
Why wrong: Preemptible nodes cause pod evictions, not gradual latency increase.
- B
The HPA's target CPU utilization is set too high, causing the autoscaler to react slowly.
A high target CPU threshold delays scaling, leading to latency.
- C
The service uses a global external HTTP(S) load balancer with session affinity.
Why wrong: Session affinity does not cause latency; it routes requests to the same backend.
- D
The application does not implement request autoscaling at the application layer.
Why wrong: Request autoscaling is not a built-in GKE concept.