You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have HPA enabled using KEDA and are trying to start using Rollouts by Referencing Deployment From Rollout.
Setup:
The following happens when we try to enable Rollouts with
"scaleDown" setting as "onsuccess" or even "progressively".
We do not set "replicas" in the Rollout Spec due to this.
When using "progressively":
Rollout starts spinning up 1 pod and terminating all the pods(except 1) in the Deployment.
HPA fails with the HPA controller was unable to get the target's current scale: rollouts.argoproj.io "<>" not found
After some time, HPA successfully triggers a scale operation. Rollout starts creating more pods (and it creates more pods in the Deployment following the scaleDown setting).
When using "onsuccess":
Rollout starts spinning up 1 pod
HPA fails with the HPA controller was unable to get the target's current scale: rollouts.argoproj.io "<>" not found
After 1 pod is started successfully, it scales down all the previous pods. Therefore, we end up having only one 1 pod of the service.
After some time, HPA successfully triggers a scale and things start getting back to normal.
Is it possible for the "scaleDown" function to check the health of HPA before triggering any scale-down?
The text was updated successfully, but these errors were encountered:
We have HPA enabled using KEDA and are trying to start using Rollouts by Referencing Deployment From Rollout.
Setup:
The following happens when we try to enable Rollouts with
When using "progressively":
the HPA controller was unable to get the target's current scale: rollouts.argoproj.io "<>" not found
scaleDown
setting).When using "onsuccess":
the HPA controller was unable to get the target's current scale: rollouts.argoproj.io "<>" not found
Is it possible for the "scaleDown" function to check the health of HPA before triggering any scale-down?
The text was updated successfully, but these errors were encountered: