KEDA doesn't validate empty array of triggers about keda

[vinod827]

When triggers is set with an empty array in ScaledObject, KEDA doesn't validate this empty value and will create a default HPA with a default 80% averageUtilization CPU resource. This can mislead users.

hmmm....that's interesting. From where this 80% of averageUtilization for CPU is coming in the HPA?

[SpiritZhou]

When triggers is set with an empty array in ScaledObject, KEDA doesn't validate this empty value and will create a default HPA with a default 80% averageUtilization CPU resource. This can mislead users.

hmmm....that's interesting. From where this 80% of averageUtilization for CPU is coming in the HPA?

It's K8s default behavior. When I create an HPA directly without metrics spec, k8s will create an HPA with 80% of averageUtilization for CPU resource.

HPA example:

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: test
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: sut
  minReplicas: 1
  maxReplicas: 10

[vinod827]

So that means HPA should not be defaulted to as a scaling option when triggers are empty in the KEDA's ScaledObject

[JorTurFer]

I think that we should validate it as part of admission hooks and also raise an error in the operator. Adding default value is quite weird as it's totally unrelated with the given triggers. This doesn't happen just with empty triggers but also when there are some issues in the creation loop

[zroubalik]

I agree, we should validate both on the Operator and validation webhook side. This is an ideal "good first issue " :)