[BREAKING CHANGE] KEDA 2.15 and KEDA 2.14 introduces multiple breaking changes in AKS v1.30+

[qpetraroia]

[BREAKING CHANGE] KEDA 2.15 and KEDA 2.14 introduces multiple breaking changes in AKS v1.30+

[ztoth123]

The impacted Azure Scaler is Azure Monitor instead of the other 2 as metricName is only used by that, right?
Where is it documented on https://keda.sh/?

[qpetraroia]

Hi @ztoth123,

Nope! Azure Monitor is safe. This is because Azure Monitor's use of metricName refers to the Azure metric name, not the name for the HPA metric.

I have checked with the upstream KEDA maintainers and the only impacted Azure scalers are Azure Blob Scaler and Azure Log Analytics Scaler.

[ztoth123]

Thanks for the answer, I see now that the metricName is deprecated and it is mentioned e.g in this doc: https://keda.sh/docs/2.10/scalers/azure-log-analytics/
"metricName - Name to assign to the metric. (Optional, if not set KEDA will generate a name based on the workspaceId. DEPRECATED: This parameter is deprecated as of KEDA v2.10 and will be removed in version 2.12)"