Using HPA in ScaledObject in restricted network environment #6158
Unanswered
rushi47
asked this question in
Q&A / Need Help
Replies: 2 comments 3 replies
-
cc: @JorTurFer |
Beta Was this translation helpful? Give feedback.
0 replies
-
The request flow is following: (ScaledObject) HPA -> K8s api server -> KEDA metrics server -> KEDA operator -> the actual metric source (the response is sent back then) |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am trying to evaluate KEDA but I wanted to confirm if it fits my scenario.
Currently we can’t use HPA as from the node where target pods are deployed, ingress is blocked on K8s API Server, lets called those node untrusted nodes.
I wanted to know if we use KEDA operator, will it work in following way:
ScaledObject (with HPA) if we specify address from where to get that metric, does HPA communicate with that metric source or its KEDA which communicates with that metric source to get that metric. We will schedule KEDA pods on trusted node, which can have access to kube api server or other metric sources
As HPA is unable to communicate with API Server from the specific nodes. So KEDA get metric from metric sources. And as KEDA is not sitting on untrusted node, KEDA can use that metric to scale down/up the deployment by communicating with kube api server.
Does KEDA work this way ?
Or it works like: KEDA spins up HPA. And then it’s HPA’s responsibility to communicate with metric sources ?
Beta Was this translation helpful? Give feedback.
All reactions