KEDA is using metrics adapter based on custom-metrics-apiserver
library. As part of the deployment, user need to specify cluster wide APIService object named v1beta1.external.metrics.k8s.io, see in the library example and in KEDA deployment .
I wonder what would happen, if user has already deployed another Metrics Adapter (which is using the same APIService based approach) and we try to install Keda. It will probably replace the original APIService definition with KEDA one, so KEDA will work, but the original stuff installed on cluster probably not. We should not break things or should make clear, that this could happen.
We should investigate what are the possibilities and whether there are a better solutions on how to deal with the metrics. Or my assumptions are wrong, so please correct me in this case.
KEDA is using metrics adapter based on custom-metrics-apiserver
library. As part of the deployment, user need to specify cluster wide
APIServiceobject namedv1beta1.external.metrics.k8s.io, see in the library example and in KEDA deployment .I wonder what would happen, if user has already deployed another Metrics Adapter (which is using the same
APIServicebased approach) and we try to install Keda. It will probably replace the originalAPIServicedefinition with KEDA one, so KEDA will work, but the original stuff installed on cluster probably not. We should not break things or should make clear, that this could happen.We should investigate what are the possibilities and whether there are a better solutions on how to deal with the metrics. Or my assumptions are wrong, so please correct me in this case.