-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Support Azure k8s Metrics Adapter for integration with HPA #152
Comments
KEDA is a cloud agnostic, vendor neutral project and thus cannot use an Azure only software component. Even for Azure services, the reliance on Azure Monitor is problematic for a multitude of reasons. KEDA has a concept of scalers - each scaler is autonomous in implementing the means by which its getting its metrics. |
That makes sense, I think my question is more why doesn't Keda integrate with existing metric servers which we can plug in. For example Ive just opened #156 for Prometheus support, which has a metrics server already, and #155 which improves Monitor support while we could plug in the one mentioned above. /cc @jeffhollan |
Was just talking about Prometheus yesterday :) Thats indeed a very powerful feature. |
Fair enough, thanks for following-up! |
Disclaimer: I haven't checked the code so this might already be the case
Why does Keda use MSFTs own metrics adapter instead of adopting the Azure k8s Metrics Adapter to integrate with the HPA?
Is it because it's based on other metrics than Azure Monitor or a different reason?
Based on the docs it's not really clear to me where it's getting the metrics from.
The text was updated successfully, but these errors were encountered: