Replies: 1 comment
-
Hey, |
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
-
Hi Team,
We are setting up keda cron to bring the deploymen replica to 0 and then scale to 3 at a particular timestamp.
Issue :- The moment we push the scaleobject yaml, the HPA triggers to bring the replicas to 0 immediately rather triggering at certain time we specified and is not working the desired manner.
Please guide us on the same
We have test deployment setup using nginx with 3 replicas.
$kubectl get all -n
NAME READY UP-TO-DATE AVAILABLE
deployment.apps/test 0/0 0 0
NAME DESIRED CURRENT READY
replicaset.apps/test-5f6778868d 0 0 0
NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS
horizontalpodautoscaler.autoscaling/keda-hpa-cron-scaledobject Deployment/test /1 (avg), /1 (avg) 1 100 0
Below yaml being used :-
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: cron-scaledobject
namespace: test
spec:
scaleTargetRef:
kind: Deployment
name: test
pollingInterval: 30
triggers:
metadata:
timezone: America/Edmonton
start: 23 * * * *
end: 27 * * * *
desiredReplicas: "0"
metadata:
timezone: America/Edmonton
start: 37 * * * *
end: 40 * * * *
desiredReplicas: "3"
Beta Was this translation helpful? Give feedback.
All reactions