Pods autoscaling not happening after 1 #7065
Replies: 1 comment
-
|
This issue is resolved |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have implemented KEDA for our application and we do see autoscaling happening from 0-1Pod and then autoscaling is not happening after that. Just 1 pod is processing all the records. We tried with 50000-100000 records in azure service bus queue but auto scaling didn't happen. Below is our code for scaled-object.
k8s/base/scaled-object.yaml
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: testsvc-scaledobject
spec:
scaleTargetRef:
name: testsvc
advanced:
horizontalPodAutoscalerConfig:
behavior:
scaleDown:
stabilizationWindowSeconds: 30
policies:
- type: Pods
value: 1
periodSeconds: 60
selectPolicy: Min
scaleUp:
stabilizationWindowSeconds: 30
triggers:
metadata:
queueName: test-queue
namespace: CHANGE_ME
messageCount: "100"
authenticationRef:
name: testsvc-auth
k8s/overlays/dev/scaled-object.yaml
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: testsvc-scaledobject
spec:
scaleTargetRef:
name: testsvc
pollingInterval: 10
minReplicaCount: 1
maxReplicaCount: 40
triggers:
- type: azure-servicebus
metadata:
queueName: test-queue
namespace: test
messageCount: "10"
authenticationRef:
name: testsvc-auth
Beta Was this translation helpful? Give feedback.
All reactions