Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support scaling to Zero with combine of Cron and cpu/mem scaler #4269

Closed
vumdao opened this issue Feb 22, 2023 · 0 comments · Fixed by #4346
Closed

Support scaling to Zero with combine of Cron and cpu/mem scaler #4269

vumdao opened this issue Feb 22, 2023 · 0 comments · Fixed by #4346
Assignees
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@vumdao
Copy link

vumdao commented Feb 22, 2023

Proposal

My scaled object

apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: app
spec:
  maxReplicaCount: 10
  minReplicaCount: 0
  scaleTargetRef:
    kind: Deployment
    name: app
  triggers:
    - metadata:
        desiredReplicas: "2"
        end: 0 21 * * *
        start: 30 7 * * *
        timezone: Asia/Ho_Chi_Minh
      type: cron
    - metadata:
        value: "85"
      metricType: Utilization
      type: cpu

I would like to scale my deployment to Zero but the cpu/mem scaler prevents that

Proposal from @zroubalik: we can allow scale to 0, in case there are multiple triggers not just cpu/mem and the activation will be driven by the non-cpu/mem scaler.

Use-Case

No response

Is this a feature you are interested in implementing yourself?

No

Anything else?

No response

@vumdao vumdao added feature-request All issues for new features that have not been committed to needs-discussion labels Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants