Container App startup trigger in k8s
Application start delay in k8s containers
Stress/Load testing applicable. When you want to sping up a lot of pods; the application inside ech pod must start simultaneously with others.
The main problem is cluster autoscaling is slow, it means additional nodes will start with delay.
AWS specific case
The idea here: prescale more nodes than required, so cluster autoscaling will not spend time to spin up new nodes
Assume we have EKS with unmanaged Node Groups as ASG. By updating Minimum capacity > 0 you will achieve, more ‘warm’ nodes that can host extra amount of pods.