You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a Rollout with an Analysis. If Rollout is scaled during the running of the Analysis, the AnalysisRun Job is terminated. Additionally, the Rollout is promoted even when the Analysis has not finished.
davcd
changed the title
HPA targeting a Rollout scales down AnalysisRun Job generated pods
AnalysisRun Job is terminated when a Scale Down event occurs
Nov 14, 2024
davcd
changed the title
AnalysisRun Job is terminated when a Scale Down event occurs
AnalysisRun Job is terminated when Rollout resource is scaled
Nov 14, 2024
After further investigation, it is possible to conclude that the issue is not related to KEDA/HPA.
Steps to reproduce and bug explanations have been simplified.
IMO this bug is critical as some people can be bypassing their application promotion conditions.
As an example, if you have some e2e or contract testing taking place before your promotion and your Rollout is scaled at the moment those Analysis are running, you will promote your new version even when the tests are not completed successfully.
Checklist:
Describe the bug
Having a Rollout with an Analysis. If Rollout is scaled during the running of the Analysis, the AnalysisRun Job is terminated. Additionally, the Rollout is promoted even when the Analysis has not finished.
To Reproduce
Having the following Rollout resource:
And scaling manually with the following command:
The bug is replicated when the following events occurs:
A new Rollout starts
Rollout is scaled (triggered by HPA or manually, doesn't matter. Also it can be scaled up or down)
Expected behaviour
Running AnalysisRun Jobs are not affected when Rollout resource is scaled.
Version
v1.7.2+59e5bd3
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: