Zhenghan Zhou
Zhenghan Zhou
Did you use an existing ScaledObject rather than a new ScaledObject to handle the existing HPA? The error that you posted in the issue will occur in that situation.
Delete the existing ScaledObject and create a new ScaledObject can take over the existing HPA even if the new one has the same name. If using the existing ScaledObject to...
What scaler are you using? Could you provide more detail info such as the scaleobject yaml?
Could you please follow the documentation(https://github.com/kedacore/keda/blob/main/CONTRIBUTING.md#changelog), update the CHANGE.MD file with the new issue, and move the documentation to https://github.com/kedacore/keda-docs?
Is it possible to add an e2e test?
Could you set --zap-log-level=debug in the keda-operator to enable debug logging and see the retrieved metric value?
From the code, it looks like the scaling is based on the total partition count instead of scaling based on the total events count. I think we should add a...
Can you describe the use case in detail? The current scalingmodifier feature may be able to meet the requirements.
@cobak78 could you help to fix the conflicts?
/run-e2e file_based_auth_test **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/17820365183)