Reduce Control Plane Requests
vlerenc opened this issue · comments
Vedran Lerenc commented
What do you suggest to change:
- KAPI
- Reduce KAPI HVPA
minAllowed
for memory (there isn't one for CPU anyway) from400M
down to200M
: #9654 - 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): #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).
- Replace HVPA with HPA and VPA on CPU and metrics (both on both):
- Dropped:
Temporary solution: https://sap-ti.slack.com/archives/C017KSLTF4H/p1713531512758829 - Accepted: Actual solution: https://gist.github.tools.sap/D043832/2051e639cf77d878f188234125c915f6
- On Hold:
Amending solution: GEP-23 tracked here
- Dropped:
- Promote the
VPAAndHPAForAPIServer
feature gate- Promote to beta
- Promote to GA (drop the existing HVPA handling)
- Reduce KAPI HVPA
- KCM:
- Reduce KCM HVPA
minAllowed
for memory (there isn't one for CPU anyway) from100M
down to50M
: #9654
- Reduce KCM HVPA
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.
Ismail Alidzhikov commented
/assign