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

[qpetraroia]

AKS will be upgrading the KEDA addon to KEDA 2.15 on AKS clusters with K8s versions >=1.31. The AKS team has added KEDA 2.14 to AKS v1.30.

KEDA 2.15 and KEDA 2.14 will introduce multiple breaking changes. The breaking changes are listed below:

• KEDA 2.15: The removal of Pod Identity support. If you use pod identity, we recommend you move over to workload identity for your authentication.

• KEDA 2.14: The removal of Azure Data Explorer 'metadata.clientSecret' as it was not safe for managing secrets. Please use clientSecretFromEnv instead.

• KEDA 2.14: Removal of the deprecated metricName from trigger metadata section. The two impacted Azure Scalers are Azure Blob Scaler and Azure Log Analytics Scaler. If you are using metricName today, please move metricName outside of trigger metadata section totrigger.name in the trigger section to optionally name your trigger.

  An example before KEDA 2.14/2.15
  
  triggers:
  - type: any-type
    metadata:
      metricName: "my-custom-name"
  
  
  An example after KEDA 2.14/2.15
  
  triggers:
  - type: any-type
    name: "my-custom-name"
    metadata:
  

[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)"

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

[microsoft-github-policy-service]

This issue will now be closed because it hasn't had any activity for 7 days after stale. qpetraroia feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

[microsoft-github-policy-service]

This issue will now be closed because it hasn't had any activity for 7 days after stale. qpetraroia feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.