Add eagerScalingStrategy for ScaledJob

[junekhan]

Added eagerScalingStrategy for ScaledJob

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
• Changelog has been updated and is aligned with our changelog requirements
• 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 #5114

Relates to #

[zroubalik]

@junekhan thanks for the contribution, could you please also cover this scenario in e2e tests?

[zroubalik]

Could you please open pr in https://github.com/kedacore/keda-docs/ to cover this new feature?

[junekhan]

Could you please open pr in https://github.com/kedacore/keda-docs/ to cover this new feature?

Sure, thanks! Will do that.

[zroubalik]

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

[junekhan]

@zroubalik Hi there, I'm sorry that the e2e test didn't go well. I'm glad to analyze the logs, although it seems that I don't have access to it.

[zroubalik]

@junekhan you should be able to access the logs by following these steps (let me know if you are not):

[junekhan]

@zroubalik Thanks for your input. I have no problem accessing the test suite log you mentioned, but I was looking for the log from inside the cluster, which can contain information about how the scaling decision was made. The test suite log only shows that the scaling didn't happen a single time, otherwise, I didn't find any clues.

[zroubalik]

@zroubalik Thanks for your input. I have no problem accessing the test suite log you mentioned, but I was looking for the log from inside the cluster, which can contain information about how the scaling decision was made. The test suite log only shows that the scaling didn't happen a single time, otherwise, I didn't find any clues.

At the bottom of the output, there's log from KEDA operator as well. That's the best we can do, you can always run the failed test locally: https://github.com/kedacore/keda/tree/main/tests#specific-test

[junekhan]

@zroubalik Thanks for your input. I have no problem accessing the test suite log you mentioned, but I was looking for the log from inside the cluster, which can contain information about how the scaling decision was made. The test suite log only shows that the scaling didn't happen a single time, otherwise, I didn't find any clues.

At the bottom of the output, there's log from KEDA operator as well. That's the best we can do, you can always run the failed test locally: https://github.com/kedacore/keda/tree/main/tests#specific-test

@zroubalik Thanks for your hint! That looks daunting 😨 but I will try.

[semgrep-app]

Semgrep found a possible database connection string built with string concatenation. Check for proper encoding/escaping of components to prevent parse errors and injection vulnerabilities.

_{Ignore this finding from db-connection-string.}

[junekhan]

Looks okay.

[junekhan]

Could you please rerun the checks? The result doesn't make sense.