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
Change KAPI HVPA maximum number of replicas and set them from 4 to 3 to better match HA clusters in 3 zones (we believe we do not need 4, if under VPA anyway, so let's get rid of that odd number): Set kubeApiserver maxReplicas: 3 #9605
Quick-fix vertical scaling after KAPIs reach 4 (3 if the above gets implemented) replicas and then going below (can then only happen for non-HA clusters), effectively freezing the vertical scaling (wasting resources from then onwards).
Why is this needed:
Primarily KAPIs but also other components waste too many resources. It would be great to address these problems, especially for KAPIs until GEP-23 lands.
The text was updated successfully, but these errors were encountered:
vlerenc
changed the title
Reduce KAPI Resources
Reduce Control Plane Requests
Apr 10, 2024
What do you suggest to change:
minAllowed
for memory (there isn't one for CPU anyway) from400M
down to200M
: Reduce minAllowed values from kube-apiserver and kube-controller-manager #9654maxReplicas: 3
#9605Temporary solution: https://sap-ti.slack.com/archives/C017KSLTF4H/p1713531512758829Amending solution: GEP-23 tracked hereminAllowed
for memory (there isn't one for CPU anyway) from100M
down to50M
: Reduce minAllowed values from kube-apiserver and kube-controller-manager #9654Why is this needed:
Primarily KAPIs but also other components waste too many resources. It would be great to address these problems, especially for KAPIs until GEP-23 lands.
The text was updated successfully, but these errors were encountered: