wide-magician-63081
02/21/2023, 3:42 PMNotReady(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/937careful-piano-35019
02/22/2023, 3:51 PMwide-magician-63081
02/22/2023, 4:00 PMimportant-oxygen-86641
02/22/2023, 4:17 PMScaledObject
Can you provide an example of an ScaledObject
that stays in that state, please?wide-magician-63081
02/22/2023, 4:42 PMapiVersion: <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"
important-oxygen-86641
02/22/2023, 4:59 PMstatus:
conditions:
- message: ScaledObject is defined correctly and is ready for scaling
reason: ScaledObjectReady
status: "True"
type: Ready
- message: Scaling is not performed because triggers are not active
reason: ScalerNotActive
status: "False"
type: Active
- status: Unknown
type: Fallback
If there is an active condition that is false, the fleet-agent set this BundleDeployment to have an activating state
- apiVersion: <http://keda.sh/v1alpha1|keda.sh/v1alpha1>
kind: ScaledObject
name: rabbitmq-consumer
namespace: default
summary:
error: true
message:
- Scaling is not performed because triggers are not active
- Resource is Ready
state: activating
ScaledObject
resource to have an Active equals to true it should fix the problem. If not, I would suggest to create an issue since it looks like fleet always mark the Bundle as error is Active is false even if Ready is true. However, that might be the expected behavior for other kubernetes resources. Therefore I'm not sure if this can be changedwide-magician-63081
02/23/2023, 10:19 AMcool-thailand-26552
02/23/2023, 2:58 PMtrue
important-oxygen-86641
02/23/2023, 3:26 PMcool-thailand-26552
02/23/2023, 5:21 PMPending
= true
or Alerted
= false
.nutritious-orange-38459
03/13/2023, 8:19 AMwide-magician-63081
03/13/2023, 8:48 AM