fix(fallback): check updated status for fallback condition instead of scaledObject#7490
Conversation
|
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:
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 checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
f281f99 to
3e65b98
Compare
|
/run-e2e fallback |
Signed-off-by: Mathis Raguin <[email protected]>
3e65b98 to
6cfadad
Compare
|
/run-e2e fallback |
Signed-off-by: Rick Brouwer <[email protected]>
|
/run-e2e fallback |
|
/run-e2e fallback |
Signed-off-by: Rick Brouwer <[email protected]>
|
/run-e2e fallback |
In
updateStatuson 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 builtstatusinstead of the original one.Checklist
make generate-scalers-schemahas been run to update any outdated generated filesFixes #7488