Repository navigation
Conversation
…goingSessions KEDA kedacore/keda#8107 (merged, shipped in KEDA 2.21.0) added includeOngoingSessions to the built-in selenium-grid scaler - the exact same trigger param, default, and calculation this chart's _helpers.tpl and this project's external scaler have carried since fixing #3167. Below KEDA 2.21.0 the built-in scaler ignores the parameter entirely, so this chart's default scalingStrategy (accurate) + the built-in scaler (autoscaling.externalScaler.enabled: false) still hits the runaway Job creation #3167 describes, even though the chart has been setting includeOngoingSessions correctly in the trigger metadata all along. Bump the keda subchart dependency floor from ^2.20.0 to ^2.21.0 so a chart-bundled KEDA install always gets the fix. Document the one case this can't reach: autoscaling.enableWithExistingKEDA with the built-in scaler brings the user's own KEDA, whose version this chart has no control over - call out the >=2.21.0 requirement there explicitly. Also fixed an adjacent stale claim that the built-in scaler is still the default; it's been externalScaler.enabled: true for a while. The external scaler itself needs no change - compared line by line against the upstream diff, it already matches exactly: same trigger metadata key (includeOngoingSessions), same default (true), and the same metric/activation-threshold calculation (.keda-external-scaler/internal/gridscaler/server.go:97-113). Verified: `helm dependency update` now locks keda to 2.21.0, `helm lint` passes, and `helm template ... --set autoscaling.externalScaler.enabled=false` still renders includeOngoingSessions correctly on the built-in-scaler trigger. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
VietND96
enabled auto-merge (squash)
October 20, 2026 02:10
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #3167. kedacore/keda#8107 (merged, shipped in KEDA 2.21.0) added
includeOngoingSessionsto the built-inselenium-gridscaler - the exact same trigger param, default (true), and metric/activation-threshold calculation this chart's_helpers.tpland this project's external scaler have already carried since fixing #3167.Below KEDA 2.21.0, the built-in scaler simply doesn't recognize
includeOngoingSessionsand ignores it. So a user on this chart's defaultscalingStrategy.strategy: accurate+ the built-in scaler (autoscaling.externalScaler.enabled: false) still hits the runaway Job creation #3167 describes on any KEDA older than 2.21.0 - even though the chart has been correctly settingincludeOngoingSessions: "false"in the trigger metadata in that combination all along; the built-in scaler just wasn't listening yet.What this does
kedasubchart dependency floor from^2.20.0to^2.21.0, so a chart-bundled KEDA install (autoscaling.enabledwithoutenableWithExistingKEDA) always gets a KEDA that honors the fix.autoscaling.enableWithExistingKEDAbrings the user's own KEDA installation, whose version this chart has no control over. Calls out the>=2.21.0requirement explicitly for that combination with the built-in scaler.externalScaler.enabled: truefor a while now, and the external scaler isn't affected by any of this since it's never relied on KEDA's own scaler code.The external scaler itself needs no change. I compared it line by line against the upstream KEDA diff: same trigger metadata key (
includeOngoingSessions), same default (true), and the same metric/activation-threshold calculation (.keda-external-scaler/internal/gridscaler/server.go:97-113vs. the upstreampkg/scalers/selenium_grid_scaler.gochange) - it was already exactly aligned, which makes sense since it's the same author's fix landed in both places.Test plan
helm dependency update charts/selenium-gridnow lockskedato2.21.0(was2.20.2).helm lint charts/selenium-gridpasses.helm template ... --set autoscaling.enabled=true --set autoscaling.scalingType=job --set autoscaling.externalScaler.enabled=falsestill renderstype: selenium-gridwithincludeOngoingSessions: "false"on the built-in-scaler trigger, matching the chart's defaultaccuratestrategy.make lint_format_scripts(helm-docs) regeneratedCONFIGURATION.md's dependency table and version badge consistently with theChart.yamlchanges.🤖 Generated with Claude Code