-
We recently built a new Github workflow that is broken down to two buckets of work
After a large bit of back and forth testing to work out the kinks, everything is running on AKS. We have it set to a minimum of 1 runner and a max of 20, so after finishing deployment of the whole workflow we have the Runner Set online and one runner is online and idle. The issue we are facing is that when we push a workflow that has 20+ builds, ARC works beautifully and quickly scales up to 20 runners, however, our AKS cluster never spins up additional nodes to back that workload so it basically crashes and no builds complete. Does anyone have any advice on how to get AKS to scale up more nodes to balance the workload? Github Workflow
Terraform for AKS cluster
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
By default AKS will run up to 110 pods per node, so unless you specify some resource request/limits AKS presumes you don't want more nodes. |
Beta Was this translation helpful? Give feedback.
I was able to get it working by adding this in values.yaml