Skip to content

manifests: CPU requests and 5 s probes for the control-plane pods - #2557

Open
Davanum Srinivas (dims) wants to merge 3 commits into
agent-substrate:mainfrom
dims:control-plane-resources
Open

Davanum Srinivas (dims) wants to merge 3 commits into
agent-substrate:mainfrom
dims:control-plane-resources

Conversation

@dims

@dims Davanum Srinivas (dims) commented Oct 13, 2026 •

Copy link
Copy Markdown
Collaborator

ate-api-server, atenet-router, ate-controller, the dataplane sidecars and the atelet ran BestEffort (atelet: 50m) beside the sandboxes; under load their 1 s probes timed out and kubelet restarted them mid-run.

Give each a CPU request, and every liveness and readiness probe a 5 s timeout and a failure threshold of 6, as postgres already has. The requests are small, 100m (ate-controller 50m): they buy Burstable QoS and CPU shares under contention and leave a 4 vCPU kind node room for the demos; size up with an overlay.

Verified on a dense kind cluster: no control-plane restarts across a full run that previously had liveness kills. go test ./cmd/ate-setup/... ./cmd/atecontroller/....

@thockin

Copy link
Copy Markdown
Collaborator

needs rebase

@dims

Copy link
Copy Markdown
Collaborator Author

needs rebase

on it!

ate-api-server, atenet-router, ate-controller and the dataplane sidecars
ran BestEffort, and the atelet reserved 50m. On a node packed with
sandboxes they got almost no CPU, their 1 s probes timed out and kubelet
restarted them mid-run. Give each a CPU request, and every liveness and
readiness probe a 5 s timeout and a failure threshold of 6, as the
postgres probes already have.
… node

The e2e kind cluster is one 4 vCPU node, and the requests summed to
about 7 CPUs together with the kubeadm pods (ate-api-server 2x1,
atenet-router 1.5, atelet 1.05, atenet-egress 0.7, ate-controller 0.5,
postgres and prometheus 0.36, kube-system 0.95), so ate-api-server
stayed Pending and the install timed out. Lower the requests to 250m
for ate-api-server, atenet-router, both envoys and atelet, and to 100m
for ate-controller, which puts the node at about 3.2 CPUs requested;
the probe settings stay. go test on cmd/ate-setup, cmd/atecontroller
and the atenet manifest tests passes, and the kind overlay renders.
…n a 4 vCPU kind node

The requests exist for Burstable QoS and CPU shares under contention, so
small values do the job and operators size up with overlays. The kind
e2e lane deploys demo pools beside ate-system and the remaining room on
a 4 vCPU node is about 1.5 CPU.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants