Hi all,

I’m encountering an issue with KEDA autoscaling while integrating it with Selenium Grid and Karpenter for node provisioning.

Scenario

• I’m running Selenium tests and want KEDA to create exactly 3 jobs when I request 3 sessions.
• However, KEDA continuously creates new jobs every few seconds until Karpenter finishes provisioning new nodes.

This results in more jobs being created than the actual number of Selenium sessions required.

Current Setup

Here is part of my values.yaml configuration:

selenium-grid:
 chromeNode:
 scaledOptions:
 minReplicaCount: 0
 maxReplicaCount: 15
 pollingInterval: 10
 autoscaling:
 enabled: true
 scalingType: job

Issue
• KEDA seems to poll the conditions too frequently (pollingInterval: 10) and creates new jobs when nodes are not yet ready.
• This causes KEDA to overscale beyond the requested session count.

Goal

I want KEDA to:
1. Create exactly 3 jobs for 3 sessions (no more, no less).
2. Avoid continuously spawning jobs while Karpenter provisions new nodes.

Proposed Solution

I believe the following changes might help resolve the issue:

1. Increase pollingInterval and add a cooldownPeriod to prevent rapid scaling:

pollingInterval: 30
cooldownPeriod: 300

2. Limit maxReplicaCount to the exact number of sessions requested:

maxReplicaCount: 3

3. Adjust KEDA triggers to scale based on exact pending Selenium sessions, possibly using Prometheus metrics.

Questions
1. How can I fine-tune KEDA’s behavior to strictly match the requested number of sessions without overscaling?
2. Are there best practices to integrate KEDA with Karpenter to ensure smooth node scaling and job creation?

Any guidance or insights would be greatly appreciated!

Thank you!