Align kops scalability configuration with kube-up
Author: serathiusCreated Mar 14, 2026Updated Jul 21, 2026
Labelskind/feature
/kind feature
After https://github.com/kubernetes/kops/pull/18069 I decided to look deeper into what other configuration has potentially changed with https://github.com/kubernetes/test-infra/pull/36137.
Came up with the following table, we should take a look and consider aligning configuration.
| Component | Configuration Option | kube-up (test-infra) | kops (run-test.sh) | Kubernetes Default | Change |
|---|---|---|---|---|---|
| Kube-APIServer | Log Level | 3 | 2 | 0 | Decreased (3 -> 2). |
| Kube-APIServer | Max Inflight | 640 | 800 | 400 | Increased (640 -> 800). |
| Kube-APIServer | Delete Workers | 16 | 100 | 1 | Increased (16 -> 100). |
| Kube-APIServer | Compaction Interval | 150s | N/A | 300s | Increased (150s -> 300s) |
| Controller Manager | QPS | 100 | 500 | 20 | Increased (100 -> 500). |
| Controller Manager | Burst | 100 | 500 | 30 | Increased (100 -> 500). |
| Controller Manager | Concurrent Node Syncs | N/A | 10 | 5 | Increased ( 5 -> 10) |
| Kube-Scheduler | QPS | 100 | 500 | 50 | Increased (100 -> 500). |
| Kube-Scheduler | Burst | 100 | 500 | 100 | Increased (100 -> 500). |
| Kubelet | API QPS | 100 | N/A | 50 | Decreased ( 100 -> 50) |
| Kubelet | Max Pods | N/A | 96 | 110 | Decreased (110 -> 96) |
/cc @upodroid @mborsz @wojtek-t @hakman
Source: kubernetes/kops