-
Notifications
You must be signed in to change notification settings - Fork 55
Description
Title: Enable the possibility to change the ControlPlane machine size
Description: In the past i've noticed that some default pods / enhancements (running on the AKS on AzureLocal) are consuming more resources than before, in one of our environments we've seen, that we're not able to run all extensions properly because we're running in resource limits...
so on a 4GB controlPlane node we're reaching the limit already with the basic pods, like calico, metallb, wyvern (read write many storage extension), velero, etc. because all or many of them have to run also on the control-plane... so it can be that metallb request already in sum 2GB of Ram... wyvern 1Gb or more.. and then the ctrl-plane is coming in the saturation ...
if you scale the ctrl plane up from 3 to 5 nodes, you've the same... because many of those pods are spawned on the new nodes and consuming the same amount of memory and brings the new nodes equally in the same saturation situation.