You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by ahinh43 May 15, 2024
I'm working on upgrading our Keda deployment from 2.11 to 2.14, and one of the changes introduced in 2.13 is the queryParameters field for the prometheus scaler. However, it's documented as a required field yet in the source code the field is marked optional.
My initial impression of reading the trigger specifications
is that missing fields under required fields would result in the request being rejected during an apply but I could be misunderstanding this.
Is there any implications for not setting queryParameters in a prometheus trigger's metadata field?
The text was updated successfully, but these errors were encountered:
Discussed in #1391
Originally posted by ahinh43 May 15, 2024
I'm working on upgrading our Keda deployment from 2.11 to 2.14, and one of the changes introduced in 2.13 is the queryParameters field for the prometheus scaler. However, it's documented as a required field yet in the source code the field is marked optional.
My initial impression of reading the trigger specifications
is that missing fields under required fields would result in the request being rejected during an apply but I could be misunderstanding this.
Is there any implications for not setting queryParameters in a prometheus trigger's metadata field?
The text was updated successfully, but these errors were encountered: