Which solution will meet these requirements with the LEAST administrative overhead?
Create a second EKS cluster. Load balance the workload between the two clusters.
Implement the Kubernetes Horizontal Pod Autoscaler. Set a target CPU utilization percentage.
Migrate the application from Amazon EKS to Amazon EC2 for the next month. Migrate the application back to Amazon EKS when the month ends.
Implement the Kubernetes Vertical Pod Autoscaler. Set a target CPU utilization percentage.
Explanations:
Creating a second EKS cluster and load balancing between the two adds significant administrative overhead and complexity. It is unnecessary for handling increased traffic.
The Kubernetes Horizontal Pod Autoscaler automatically scales the number of pods based on CPU utilization, which is the simplest and most efficient solution to handle traffic spikes with minimal manual intervention.
Migrating to EC2 for a short period adds unnecessary complexity and operational overhead. It also requires manual migration back to EKS after a month.
The Kubernetes Vertical Pod Autoscaler adjusts resource requests for individual pods, but it does not scale the number of pods, which is the requirement for handling increased traffic.
As far as I’m aware, the answer is:
Implement the Kubernetes Horizontal Pod Autoscaler. Set a target CPU utilization percentage.
I strategize that the answer is:
Implement the Kubernetes Horizontal Pod Autoscaler. Set a target CPU utilization percentage.