Hello everybody, I'm contacting you because I'm trying to set up Keda and as usual I want to use Fleet to deploy its objects. Keda is installed (still KubeVersion problem but that's not the topic here. I deployed a fleet that contains a helm chart of a project of mine with, among other things, two deployments and 2 ScaledObject. Just like the HPAs, Keda modifies the replicas so I added a diff in fleet and it works fine. On the other hand, ScaledObject objects have an “Activating” status when the trigger is pending. This is a normal status (from what I understand). But Rancher sees it in error on its UI and the bundle is also in error.

NotReady(1) [Bundle ebad]; scaledobject.keda.sh ebad-ma7/ebad-back error] Scaling is not performed because triggers are not active, Resource is Ready; scaledobject.keda.sh ebad-ma7/ebad-back modified {"spec":{"triggers":[{"metadata":{"desiredReplicas":"2","end":"35 14 * * *","start":"29 14 * * *","timezone":"Europe/Paris"},"type":"cron"}]}}; scaledobject.keda.sh ebad-ma7/ebad-front error] Scaling is not performed because triggers are not active, Resource is Ready

Is there a way to ignore this type of status? I think it's related to this issue: https://github.com/rancher/fleet/issues/937

Hi Damien. That's clearly interesting, and I am interested in what you might be able to achieve with Keda combined with Fleet.

Hi Paul, We use Fleet to deploy our user's applications helm charts. We try to integrate keda for several use cases (run app only from 08:00am to 6:00pm or scale app based on Kafka topics). To do this, we have the "ScaledObject" CR in the helm chart.

Hi Damien, I'm not sure if it is related to https://github.com/rancher/fleet/issues/937 as this is only for jobs. It looks like this problem happens with the CR

ScaledObject

Can you provide an example of an

ScaledObject

that stays in that state, please?

Hi, for sure :

apiVersion: <http://keda.sh/v1alpha1|keda.sh/v1alpha1>
kind: ScaledObject
metadata:
  name: ebad-back
spec:
  minReplicaCount: 0
  maxReplicaCount: 2
  scaleTargetRef:
    name: {{ .Values.backend.name }}-backend
  triggers:
    - type: cron
      metadata:
        timezone: Europe/Paris
        start: 29 14 * * *
        end: 35 14 * * *
        desiredReplicas: "2"

I installed Keda, then applied this ScaledObject but it looks like I'm missing more things. I'll try to reproduce it tomorrow with the examples from https://github.com/turbaszek/keda-example

Hi Raul, Thank you for your analyse. Yes, this is the behaviour of Keda (I have the same behaviour with a Cis ClusterScan which have a failure). So, I'm going to create an issue on Fleet project. Regards

@important-oxygen-86641 The problem seems to happen also for CIS Scans that did complete successfully but have a rule that is not satisfied. For example, the scan shown in screenshots should not be in Error because the scan is actually completed, but a couple of rules are not satisfied. Fleet should only consider `Created`equals

true

Probably the ClusterScan CR has other conditions not satisfied

There is a screenshot of that above. The possible culprits are

Pending

=

true

or

Alerted

=

false

.

@wide-magician-63081 Did you find any way to work around this in the mean time?

Hi @nutritious-orange-38459, No I didn't find a work around.