You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warning ScaledObjectCheckFailed 47m (x9 over 47m) keda-operator Target resource doesn't exist
Warning ScaledObjectCheckFailed 47m (x9 over 47m) keda-operator ScaledObject doesn't have correct scaleTargetRef specification
Normal KEDAScalersStarted 47m keda-operator Started scalers watch
Normal ScaledObjectReady 47m (x3 over 47m) keda-operator ScaledObject is ready for scaling
Warning KEDAScalerFailed 47m keda-operator error inspecting rabbitMQ: Exception (404) Reason: "NOT_FOUND - no queue 'inference_queue' in vhost '/'"
Normal KEDAScalersStarted 2m31s (x719 over 47m) keda-operator Scaler rabbitmq is built.
but my hpa was as follows
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: my-microservice-scaledobject
namespace: dev
spec:
scaleTargetRef:
name: my-microservice # The name of your deployment
pollingInterval: 5 # Time interval to poll RabbitMQ queue for messages
cooldownPeriod: 30 # Time to wait before scaling down after scaling up
minReplicaCount: 0 # Minimum replicas can scale to 0
maxReplicaCount: 20 # Maximum replicas (adjust based on your needs)
triggers:
type: rabbitmq
metadata:
host: "amqp://admin:Truefan@[email protected]:5672" # Correct RabbitMQ URL
queueName: "inference_queue" # The RabbitMQ queue name to monitor
vhost: "naveen-test-dev" # The vhost name (ensure this is the correct vhost in RabbitMQ)
queueLength: "1" # Scale 1 pod per message in the queue
i was the file name as hpa.yml and the deploying in the dev namespace and keda operator in the keda namespace can any help me with this
Hey everyone. I have this RunnerDeployment resource:
and I have this keda scaled object for that RunnerDeployment resource:
Even though scaleTargetRef looks correct it's not scaling down to 0. These are the logs I see:
If anyone could help that will be great.
Thanks
The text was updated successfully, but these errors were encountered: