HTTP Add-on Doesn't Reflect Updated Concurrency Values in Scaler Object

[MikelSeron]

Report

When using the KEDA HTTP add-on to scale based on HTTPS request concurrency, the scaling works perfectly when the scaler object is first created with the desired concurrency values. However, if the existing scaler object is edited to modify the concurrency values, the changes are not reflected in the scaling behavior.

Even though the manifest reflects the updated concurrency value, the scaling process still uses the old values. This behavior persists despite ensuring that the manifest has been correctly applied.

Expected Behavior

After applying an updated scaler manifest with new concurrency values, the KEDA HTTP add-on should immediately reflect and use the updated values in scaling decisions.

Actual Behavior

After applying an updated scaler manifest with new concurrency values, the KEDA HTTP add-on should immediately reflect and use the updated values in scaling decisions.

Steps to Reproduce the Problem

1. Create a scaler using the KEDA HTTP add-on with specific concurrency values.
2. Confirm that scaling works as expected with the initial concurrency values.
3. Edit the scaler object to change the concurrency values in the manifest.
4. Apply the updated manifest.
5. Observe that the scaling process still uses the old concurrency values.

Logs from KEDA HTTP operator

No response

HTTP Add-on Version

0.8.0

Kubernetes Version

1.30

Platform

Microsoft Azure

Anything else?

Workaround (if any):
Deleting and recreating the scaler object with the desired concurrency values resolves the issue but is not ideal for production environments.