KEDA Addon still deploys 2.14.1 in AKS 1.30+

[jblaaa-codes]

Report

I am looking to take advantage of some of the newer features of KEDA provided in 2.15. I am using the managed KEDA addon with AKS. When I upgraded AKS to 1.30.x the addon is not upgrading above 2.14.1. I also tried to spin up a brand new cluster and install the addon from scratch and it appears to still roll out 2.14.1.

https://learn.microsoft.com/en-us/azure/aks/keda-deploy-add-on-arm

the text in the doc, I'm not sure if it means I must do something else to enable a preview version? I assume if I'm on 1.30+ I should get upgraded but maybe I'm wrong and wanted to check.

_KEDA version 2.15+ introduces a breaking change that removes pod identity support. We recommend moving over to workload identity for your authentication if you're using pod identity. While the KEDA managed add-on doesn't currently run KEDA version 2.15+, it will begin running it in the AKS preview version 1.31.

For more information on how to securely scale your applications with workload identity, please read our tutorial. To view KEDA's breaking change/deprecation policy, please read their official documentation._

Expected Behavior

If I upgrade to a supported version of AKS, the addon should auto-upgrade KEDA to the latest supported version.

Actual Behavior

KEDA does not upgrade past 2.14.1

Steps to Reproduce the Problem

1. Deploy AKS with a version above 1.30
2. use the azure CLI to deploy the KEDA add on
3. run kubectl describe %keda-operator-pod% | grep version #<-- will return version 2.14.1

Logs from KEDA operator

example

KEDA Version

2.14.0

Kubernetes Version

1.31

Platform

Microsoft Azure

Scaler Details

No response

Anything else?

No response

[jblaaa-codes]

anyone able to answer if this is by design or if it's a bug yet? Thank you.

[jemag]

Your issue is with the AKS addon not KEDA itself. Should probably either open a ticket with Azure or create an issue on the AKS github.

[jblaaa-codes]

I did open a sev C ticket and they sat on it saying support would be limited and asked me what the KEDA core team says. TrackingID#2503130040013082

From the ticket:

I hope you doing well.

We have discussed your query internally and gathered some information. Unfortunately, your request falls outside the scope of our current technology. However, we have provided some details below that may help address your query. We hope this information proves useful. Should you have any further questions or need additional assistance, please do not hesitate to reach out.

To upgrade the KEDA add-on to version 2.15+ on your Azure Kubernetes Service (AKS) cluster, you need to ensure that your AKS cluster is running a compatible Kubernetes version. Here are the key points and steps to follow:

Key Points:

Kubernetes Version Dependency:

KEDA 2.14 is installed on AKS clusters running Kubernetes version 1.30.

KEDA 2.15 is installed on AKS clusters running Kubernetes version 1.31 or later.