Azure / Azure/AKS

[Feature] Keda Customization when installed through terraform workload_autoscaler_profile

Open
#5,027 4 comments 0 reactions 1 assignee Assigned to @colinmixonn View on GitHub
feature-request KEDA
Dominant language
TypeScript
Stars
2.1k
Forks
395
Avg merge
4d 15h
Merged PRs (30d)
15

Description

**Issue**
We cannot change the KEDA_HTTP_DEFAULT_TIMEOUT to some other value than the default 3000ms. Keda is installed on AKS Version 1.31 through Terraform with latest Azurerm Provider through this block ```workload_autoscaler_profile {
keda_enabled = var.keda_enabled
}```
Even after patching the ```keda-operator``` deployment on ```kube-system``` namespace, this is being overwritten to default value every few minutes, because it is managed from AKS.

**I tried the solution below**
Patched ```kube-system/keda-operator``` deployment through the command ```kubectl edit deployment keda-operator -n kube-system``` , located the timeout value and changed it to my preferences.
This worked fine, but every few minutes, the Keda Deployment is reconciled from Azure, and it reverts to default value 3000.
This does not apply to other arguments like ```KEDA_SCALEDJOB_CTRL_MAX_RECONCILES``` , because I found through Copilot that this is a non-managed argument as per screenshot:

![Image](https://github.com/user-attachments/assets/fb916608-2bb0-4cf3-abe6-9fc135cdce57)

**Possible Solution**
Edit the block https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/kubernetes_cluster#keda_enabled-1 similar to:
```
workload_autoscaler_profile {
keda_enabled = true
keda_env { KEDA_HTTP_DEFAULT_TIMEOUT = , KEDA_SCALEDJOB_CTRL_MAX_RECONCILES = , OTHER_ARGUMENT = }
}
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.