-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ScaledObject with argo Rollout scaleTargetRef fails to reconcile #4344
Comments
Hello, |
In the error message I can see: |
@zroubalik, i use the above ClusterTriggerAuthentication configuration. It works when I use Deployment, when I use Rollout with embedded pod spec. The error occurs only when I use Rollout with workloadRef. Here is the problematic Rollout:
|
@JorTurFer , here are more logs:
|
@golanpa gotcha, the problem is that |
@zroubalik, thanks for the insight. Is there a request for that? should we transition this "bug" to a feature request? |
@golanpa did that. Are you willing to contribute this? |
@zroubalik , i will try to take a look at that |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Report
ScaledObject with Argo Rollout scaleTargetRef fails to reconcile in GKE and HPA resource is not created.
I am using Keda 2.9.3 (installed via https://kedacore.github.io/charts, version: 2.9.4).
Expected Behavior
HPA resource should be created for the ScaledObject.
Actual Behavior
Reconciliation fails with the following error and HPA resource is not created.
If a Deployment ref is used then the reconciliation succeeds, e.g:
Steps to Reproduce the Problem
Having an Argo Rollout resource named archive-creator use the following Keda resources:
ScaledObject:
ClusterTriggerAuthentication:
Logs from KEDA operator
KEDA Version
2.9.3
Kubernetes Version
None
Platform
Google Cloud
Scaler Details
gcp-pubsub
Anything else?
No response
The text was updated successfully, but these errors were encountered: