Skip to content

fix(fallback): check updated status for fallback condition instead of scaledObject#7490

Merged
rickbrouwer merged 4 commits into
kedacore:mainfrom
Sayrus:use-new-status
Mar 15, 2026
Merged

fix(fallback): check updated status for fallback condition instead of scaledObject#7490
rickbrouwer merged 4 commits into
kedacore:mainfrom
Sayrus:use-new-status

Conversation

@Sayrus

@Sayrus Sayrus commented Feb 26, 2026

Copy link
Copy Markdown
Contributor

In updateStatus on fallback, Health is checked against the current ScaledObject instead of the newly built health status. This means that Fallback status is only be updated on the next loop. This doesn't create any significant issue but can lead to some anomalies when reviewing ScaledObject statuses. This PR aims at fixing this by comparing the newly built status instead of the original one.

Checklist

  • When introducing a new scaler, I agree with the scaling governance policy
  • I have verified that my change is according to the deprecations & breaking changes policy
  • Tests have been added (if applicable)
  • Ensure make generate-scalers-schema has been run to update any outdated generated files
  • Changelog has been updated and is aligned with our changelog requirements, only when the change impacts end users
  • A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
  • A PR is opened to update the documentation on (repo) (if applicable)
  • Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #7488

@Sayrus Sayrus requested a review from a team as a code owner February 26, 2026 15:34
@github-actions

Copy link
Copy Markdown

Thank you for your contribution! 🙏

Please understand that we will do our best to review your PR and give you feedback as soon as possible, but please bear with us if it takes a little longer as expected.

While you are waiting, make sure to:

  • Add an entry in our changelog in alphabetical order and link related issue
  • Update the documentation, if needed
  • Add unit & e2e tests for your changes
  • GitHub checks are passing
  • Is the DCO check failing? Here is how you can fix DCO issues

Once the initial tests are successful, a KEDA member will ensure that the e2e tests are run. Once the e2e tests have been successfully completed, the PR may be merged at a later date. Please be patient.

Learn more about our contribution guide.

@snyk-io

snyk-io Bot commented Feb 26, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@keda-automation keda-automation requested a review from a team February 26, 2026 15:35
@rickbrouwer

rickbrouwer commented Feb 27, 2026

Copy link
Copy Markdown
Member

/run-e2e fallback
Update: You can check the progress here

@rickbrouwer rickbrouwer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@rickbrouwer rickbrouwer added the Awaiting/2nd-approval This PR needs one more approval review label Feb 27, 2026
@keda-automation keda-automation requested a review from a team February 27, 2026 15:20
@rickbrouwer

rickbrouwer commented Feb 27, 2026

Copy link
Copy Markdown
Member

/run-e2e fallback
Update: You can check the progress here

@rickbrouwer rickbrouwer changed the title fix: use deepcopied and modified status to determine fallback condition fix(fallback): check updated status for fallback condition instead of scaledObject Mar 9, 2026
@rickbrouwer rickbrouwer enabled auto-merge (squash) March 9, 2026 16:32
Comment thread CHANGELOG.md Outdated
Signed-off-by: Rick Brouwer <[email protected]>
@rickbrouwer

rickbrouwer commented Mar 9, 2026

Copy link
Copy Markdown
Member

/run-e2e fallback
Update: You can check the progress here

@keda-automation keda-automation requested a review from a team March 9, 2026 16:34
@rickbrouwer

rickbrouwer commented Mar 9, 2026

Copy link
Copy Markdown
Member

/run-e2e fallback
Update: You can check the progress here

@rickbrouwer

rickbrouwer commented Mar 12, 2026

Copy link
Copy Markdown
Member

/run-e2e fallback
Update: You can check the progress here

@rickbrouwer rickbrouwer merged commit 1c6c09b into kedacore:main Mar 15, 2026
44 of 47 checks passed
@rickbrouwer rickbrouwer removed the Awaiting/2nd-approval This PR needs one more approval review label Apr 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ScaleToZero doesn't reset Fallback status leading to issues if the previous state was a failure

3 participants