It is not possible to add valid triggers when creating ScaledObject from the OCP Console

[dgrisonnet]

When creating ScaledObject from the OCP Console, it is not possible to specify trigger-specific fields such as the serverAddress and the metricName for the Prometheus scaler. As such, it is not possible to create a valid ScaledObject from the Console without having to modify the resource afterward.

Expected Behavior

I would have expected to be able to configure a valid Prometheus trigger from the OCP Console.

Actual Behavior

These were the only fields I was able to configure:

From a UX perspective, I would've expected the type field to be a drop-down list where I could have chosen the type I wanted to use, and then it would have displayed the scaler-specific fields for me to configure.

Steps to Reproduce the Problem

1. Install Keda via OLM
2. Create ScaledObject from the Console

Specifications

• KEDA OLM Operator Version: latest
• KEDA Version: 2.4.0
• Platform & Version: 4.10
• Kubernetes Version: 1.22
• OLM Version:

[zroubalik]

Agree, that would be really nice, the problematic part is that trigger metadata are map[string]string thus it is not that straightforward to implement this request :(