-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BREAKING CHANGE] KEDA 2.15 and KEDA 2.14 introduces multiple breaking changes in AKS v1.30+ #4471
Comments
The impacted Azure Scaler is Azure Monitor instead of the other 2 as |
Hi @ztoth123, Nope! Azure Monitor is safe. This is because Azure Monitor's use of I have checked with the upstream KEDA maintainers and the only impacted Azure scalers are Azure Blob Scaler and Azure Log Analytics Scaler. |
Thanks for the answer, I see now that the |
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. |
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. |
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. |
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 movemetricName
outside of trigger metadata section totrigger.name
in the trigger section to optionally name your trigger.The text was updated successfully, but these errors were encountered: