chore(deps): update helm release keda to v2.20.2 - #164
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Helm Template Diff —
|
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — PR body has a real, categorized ### Release Notes (Improvements/Fixes); one matching diff comment (03-apps-apps-keda) present. |
| Description vs. diff | Consistent — sole file changed is 03_apps/apps/keda/app.yaml (helm.version: 2.20.1 → 2.20.2), matches the PR table, no scope beyond the keda app. |
| Rendered diff | Full, no truncation (166 changed lines, all shown) — mostly cosmetic label/version bumps and image tag bumps, plus additive CRD schema changes and three new operator startup args (--http-max-idle-conns=0, --http-max-idle-conns-per-host=1000, --http-idle-conn-timeout=90s, matching the changelog's "share HTTP transports across scalers" fix). One genuine RBAC rule change (below). |
| RBAC | ClusterRole/keda-operator — an existing rule's apiGroups gains "" alongside events.k8s.io for the events resource (verbs unchanged, not shown as they didn't diff). This matches the changelog's "Restore core "" API group in events RBAC so client-go's event broadcaster can write legacy events" fix — additive, narrow (events only, not secrets/pods/nodes), but it's a cluster-scoped grant change, so per policy it's treated as at least Medium on its own. |
| Changelog vs. config | No overlap with live config — 03_apps/apps/keda/values.yaml sets only networkPolicy.enabled: true; nothing there touches RBAC, CRD strategy fields, or HTTP transport settings. |
Details:
- CRD schema (owned by keda, group
keda.sh/eventing.keda.sh):scalingStrategy.strategyenum gainsdefault(matches "Fix ScaledJob CRD validation to include 'default' as a valid value" exactly);containerPortschemas gain a requiredprotocolfield (×3, in CRDsscaledjobs.keda.sh);stabilizationWindowSecondsgainsminimum: 0/maximum: 3600bounds; ametricTypefield description is removed from a nested block in the same CRD area — all additive/tightening, none removes anything this repo instantiates. - §6.6 cross-component check ran (keda owns CRDs and the changelog explicitly calls out a CRD validation fix): grepped the repo outside
03_apps/apps/keda/forkeda.sh/eventing.keda.shinapiVersion:fields — zero hits. No other component in this repo createsScaledObject/ScaledJob/TriggerAuthentication/CloudEventSourceresources, so the CRD schema changes have no live blast radius. 03_apps/apps/keda/app.yamlrequestsadditionalNamespaces: [kube-system]for the external-metrics ClusterRoleBinding — unrelated to this bump, unchanged.
Why MEDIUM: solely due to the ClusterRole/keda-operator rule change — a cluster-scoped RBAC grant addition is treated as at least Medium regardless of how narrow or well-documented it is; everything else in this diff is cosmetic or additive with no live-config overlap.
Generated by Claude Code
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.
This PR contains the following updates:
2.20.1→2.20.2Release Notes
kedacore/keda (keda)
v2.20.2Compare Source
Improvements
HPAActivecondition onScaledObjectmirroring the HPA's ownScalingActivestatus, so transient HPA metric gaps no longer flip theReadycondition toFalse(#7914)Fixes
CertPool(#7910)TriggerAuthenticationwhenawsSecretManager.credentialsis omitted and noawsSecretManager.podIdentityis set (#7927)customScalingStrategy.GetEffectiveMaxScalewhencustomScalingQueueLengthDeductionis omitted; the optional field is now treated as zero deduction instead of panicking (#7798)GetCurrentReplicaswhen a Deployment/StatefulSet/ReplicaSet is returned from the informer cache with an undefaultedspec.replicas; a nil value is now treated as the Kubernetes default of 1 instead of panicking (#7863)ScaledJobCRD validation to include "default" as a valid value forscalingStrategy.strategy(#7855)GetCurrentReplicasagainst nilStatus.ScaleTargetGVKRto prevent operator panics under the cache race documented in (#4389) / (#4955)""API group in events RBAC so that client-go's event broadcaster can write legacy events (#7922)BackoffinWithConnectParamsdisabled backoff and caused a zero-delay reconnect loop that flooded logs when keda-operator was unreachable (#7856)globPatternnever matching when written in path-style with a leading/, since blob names never have one (#6492)Pingfails so the background topology-monitoring connections opened bymongo.Connectare not leaked (#5612)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.