# Need suggestion in scale worker from 0 to 1 with keda

**URL:** <https://community.temporal.io/t/need-suggestion-in-scale-worker-from-0-to-1-with-keda/11404>\
**Category:** Community Support\
**Tags:** metrics, worker, kubernetes\
**Created:** [March 17, 2024, 5:53am UTC](https://community.temporal.io/t/need-suggestion-in-scale-worker-from-0-to-1-with-keda/11404 "2024-03-17T05:53:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ddj](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/ddj/32/4029_2.png) [@ddj](https://community.temporal.io/u/ddj)\
**Post date:** [March 17, 2024, 5:53am UTC](https://community.temporal.io/t/need-suggestion-in-scale-worker-from-0-to-1-with-keda/11404/1 "2024-03-17T05:53:24Z")

</div>

We have a workflow that only run seldomly and the workflow is not latency sensitive so we would like to find a way to scale to 0 when no running activity and scale to 1 or more when there’s work comes in.

It seems temporal’s overall suggestion is using `worker_task_slots_available` or `activity_schedule_to_start_latency ` to scale worker, but I guess both won’t work well for 0-\>1 scale. And what we need is the task queue length. Unfortunately, I cannot find any metric that reflects that.

I also find this similar topic: [Worker integration with KEDA scaling](https://community.temporal.io/t/worker-integration-with-keda-scaling/8056) It seems temporal team will work with keda to add more metric to support, not sure if anyone can share the timeline?

---

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [March 20, 2024, 4:03pm UTC](https://community.temporal.io/t/need-suggestion-in-scale-worker-from-0-to-1-with-keda/11404/2 "2024-03-20T16:03:55Z")

</div>

Hi @ddj

I think for now, you will need at least one worker running or have a way, externally, to start a worker when there is work coming.

There is an issue open for Keda. You can watch [Add workers autoscaling through KEDA · Issue #33 · temporalio/temporal · GitHub](https://github.com/temporalio/temporal/issues/33); there is no ETA I am aware of.

Regards,  
Antonio