Keep hpa active when one of triggers failed about keda

[JorTurFer]

Hello @Frezyy123
I think that having more control over the fallback, it's an interesting scenario to go deeper. I don't know how can we design this for being more flexible without being too complex. Do you have any idea/proposal about the design? (at high level)

[Frezyy123]

I assume that it should be configure like:

triggers:
    - type: cpu
      metricType: Utilization
      metadata:
        value: "50"
    - type: prometheus
      metadata:
         query: rate(my_beatuful_metric[1m])
         threshold: "3"
         skipFailing: true

Default behaviour is skipFailing: false (I guess skipFailing is better name), because we don't want breaking changes. So if you don't enable this option it will work the same as before
So controller just exclude failing metric and handle with cpu trigger only. When prometheus is reachable prometheus trigger works again.
I am not sure that it will be easy to realise, so I need a little bit more time for research

Fallback will work the same. If at least one of triggers without skipFailing: true fails, we set fallback values for hpa.

[JorTurFer]

@tomkerkhove @zroubalik WDYT?

About the proposal, I'd move the skipFailing property from metadata to the trigger spec directly

[zroubalik]

Yes, I think this is doable, we should move it out of the metadata section. I don't like the name though :)