Hi Ole, I ran into you post because I was looking for a better performance of EKS autoscaling. I was testing you solution on EKS but it didn't work as you said. I enabled the warmpool in one of the ASG and the nodes are created on EKS and they are as notReady. The problem is when I scale-up a deployment, CAS doesn't put as Ready this nodes, it creates new nodes. Is there any CAS configuration necessary to work with the warmpool?
Thank you!!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Ole, I ran into you post because I was looking for a better performance of EKS autoscaling. I was testing you solution on EKS but it didn't work as you said. I enabled the warmpool in one of the ASG and the nodes are created on EKS and they are as notReady. The problem is when I scale-up a deployment, CAS doesn't put as Ready this nodes, it creates new nodes. Is there any CAS configuration necessary to work with the warmpool?
Thank you!!