-
Notifications
You must be signed in to change notification settings - Fork 1.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
Issue with GCP PubSub scaledObject #5093
Comments
I think that the solution in the code is just adding the default value during keda/pkg/scalers/gcp_pubsub_scaler.go Lines 66 to 71 in d48475b
|
Signed-off-by: Jim Gustavsson <jim.a.gustavsson@gmail.com>
Signed-off-by: Jim Gustavsson <jim.a.gustavsson@gmail.com>
…#5099) Signed-off-by: Yoon Park <yoongon.park@gmail.com>
@JorTurFer I could see this has been fixed but i am getting the same error when i tried.
|
The fix is solved because the PR is merged, but it hasn't been released yet. You can check the first release where the PR is included, checking the PR directly: And this other PR has a fix already released: You can expect this fix released on Jan release |
Thanks for the information! |
…#5099) Signed-off-by: anton.lysina <alysina@gmail.com>
Discussed in #4751
Originally posted by raghu-manne June 29, 2023
I am trying to test out keda with GCP pubsub andd the getting below error. Any insights where am i doing wrong?
2023-06-29T11:26:13Z ERROR Reconciler error {"controller": "scaledobject", "controllerGroup": "keda.sh", "controllerKind": "ScaledObject", "ScaledObject": {"name":"test","namespace":"default"}, "namespace": "default", "name": "test", "reconcileID": "5b54cc98-02bf-4dea-a270-125a70a957b5", "error": "HorizontalPodAutoscaler.autoscaling \"keda-hpa-test\" is invalid: spec.metrics[0].external.target.averageValue: Invalid value: resource.Quantity{i:resource.int64Amount{value:0, scale:0}, d:resource.infDecAmount{Dec:(*inf.Dec)(nil)}, s:\"0\", Format:\"DecimalSI\"}: must be positive"}
My scaledobject looks like this
Scaledobject events says this
The text was updated successfully, but these errors were encountered: