[Fix] Increasing k8s setting to handle overwhelming requests in devbox.

[0yukali0]

Why is this proposal?

flyte-benchmark` triggers overloading problem in liteSQL and k8s API server.

Related Issues

Related #7757

What to do?

Update k3s setting with following arguments.

"--kube-apiserver-arg=max-requests-inflight=3000", \                                                                                                                                               
"--kube-apiserver-arg=max-mutating-requests-inflight=3000"                                                                                                                                                                                                                                                                     
"--kube-controller-manager-arg=kube-api-burst=3000"                                                                                                                                           
"--kube-controller-manager-arg=kube-api-qps=3000"                                                                                                                                         
"--kubelet-arg=max-pods=300"                                                                                                     
"--kubelet-arg=system-reserved=cpu=1500m,memory=3Gi"    #Optional, enable it when no resource reserved for kubelet                                                                                                       
"--kubelet-arg=kube-reserved=cpu=500m,memory=1Gi" #Optional, enable it when no resource reserved for kubelet         

How to reproduce?

# git clone flyte
make devbox-build
make devbox-run
# git clone flyte-benchmark
uv run scripts/v2/swarm.py       --k 25 --n 2000

Screenshots

-k 10 -n 2000 triggers K8S Api error from k8s api server.

[runllm]

It could be possible that the specific k3s arguments you listed (such as --kube-apiserver-arg=max-requests-inflight=3000, --kubelet-arg=max-pods=300, etc.) are not explicitly documented in the provided Flyte data sources for devbox configuration or k3s setup. The official Flyte devbox setup uses k3d and Docker, but there is no mention of passing these advanced k3s arguments directly in the standard devbox workflow or Makefile commands according to CONTRIBUTING.md and the devbox implementation in flyte-sdk/_devbox.py.

Though I'm not entirely certain, it might be that to apply such custom k3s arguments, you would need to modify the underlying k3d cluster creation command or Docker entrypoint for the devbox image, but this is not described in the official docs or code. The use of ETCD instead of LiteSQL is also not covered in the standard devbox instructions. Would you like more detail on how to potentially patch the devbox setup to inject these arguments, or guidance on where in the codebase such changes could be made?

Sources:

• CONTRIBUTING.md
• flyte-sdk/_devbox.py

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @Herald to ask follow-up questions. See runllm.com for more!

[0yukali0]

#take