Description
Report
We are a centralised team which is providing keda agents for the whole organisation within a single cluster. This means we are scaling a lot of keda jobs.
Issue :
We have encountered an issue where if an Organisation has parallel license count of 1 and they queue 100 jobs, Keda will already start reserving IP's for all the queued jobs. This cause resource lock and also cause our subnets to run out of IP addresses
Expected Behavior
While polling and queuing pods, keda should respect license count available at the Organization level in Azure DevOps
Actual Behavior
Keda doesn't respect the license count and already assign IP to pods created although azure pipelines cannot process the jobs since available license count is not there to handle all the jobs
Steps to Reproduce the Problem
- Create an agent pool in Azure DevOps and corresponding namespace in cluster with keda
- Have a parallel license count set to a number e.g 1 in azure devops organisation for Self hosted agents
- Queue a dummy pipeline 10 times and put a sleep in there e.g for 10 mins
Logs from KEDA operator
example
KEDA Version
2.12.0
Kubernetes Version
< 1.26
Platform
Amazon Web Services
Scaler Details
Azure Pipelines
Anything else?
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Proposed