Remove replicas if KEDA is enabled#29838
Conversation
|
needs static checks fixes and rebase. |
bba7fbf to
6ae4686
Compare
|
Done, @potiuk. |
|
Looks like there are some side-effects of that change - the errors look quite related. |
|
Nope. It happens in main - we need to fix it there first. |
|
Can you please rebase @mabrikan -> I think the errors you see should have been fixed in main already, but it's good to double-check it. |
|
Sure thing 👍 |
potiuk
left a comment
There was a problem hiding this comment.
Looks good now. And the explanation is plausible. @jedcunningham @dstandish - any problem you see with removing replicas in this case?
|
I read a bit more and yeah - that's also official recommendation for HPA to not set replicas, so it should be OK to merge. https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#replicas @dstandish @jedcunningham - shout if you think otherwise :) |
Remove
replicasfield in workers Deployment/StatefulSet if KEDA is enabledGitOps operators (e.g. ArgoCD) complain when the manifest is changed due to KEDA/HPA auto-scaling. The good practice is to remove
replicasfield when auto-scaling is used.Reference:
https://argo-cd.readthedocs.io/en/stable/user-guide/best_practices/#leaving-room-for-imperativeness