Azure / Azure/azure-functions-core-tools

No scaler found for timertrigger. func deploy generated scaledobject

Open
#1,926 12 comments 4 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
1.5k
Forks
498
Avg merge
5d 4h
Merged PRs (30d)
15

Description

Hello, I am trying to deploy to kubernetes an Azure Functions v3 project that has several Http Functions and one TimerTrigger function, and I see the created scaled object is the one below after executing the following command:

func kubernetes deploy --name timered --registry localhost:5000 --namespace

The default configured replicas are zero

```yaml
uid: a8cdf04d-178f-4cdd-8add-aa455219cf28
spec:
maxReplicaCount: 5
minReplicaCount: 1
pollingInterval: 5
scaleTargetRef:
deploymentName: timered
triggers:
- metadata:
name: myTimer
schedule: '*/5 * * * * *'
type: timerTrigger
type: timertrigger
kind: List
```

I do not know what is the purpose of creating a trigger with type "timertrigger", as It seems it does not exist in keda, or maybe I am missing something?

The logs of the keda operator reflect the following error, and the deployment always has zero replicas.

"Reconciler error","controller":"scaledobject-controller","request":"delete/timered","error":"error getting scaler for trigger #0: no scaler found for type: timertrigger"

Are timertriggers thought to be working with ScaledObjects? Or can we get rid of the scaled object definition and just use an standard HPA and configure replicas in the deployment?

Thanks

Contributor guide

Open the contributing guide

Research direction

Start with the `func kubernetes deploy` path and reproduce the generated ScaledObject for a project containing a TimerTrigger. Compare its `timertrigger` entry with the KEDA operator error and supported scaler types. Done means the deployment produces a valid scaling configuration or clearly avoids creating an unsupported ScaledObject for TimerTrigger functions.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, kubernetes
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.