Skip to content

hack: ATE_KIND_RESERVED_CPU reserves kubelet and system CPU on kind nodes - #2495

Merged
Benjamin Elder (BenTheElder) merged 2 commits into
agent-substrate:mainfrom
dims:kind-kube-reserved
Oct 15, 2026
Merged

Benjamin Elder (BenTheElder) merged 2 commits into
agent-substrate:mainfrom
dims:kind-kube-reserved

Conversation

@dims

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

Copy link
Copy Markdown
Collaborator

Dense nodes starve the kubelet's heartbeat; after the 300 s toleration the taint manager evicts the node's pods.

  • ATE_KIND_RESERVED_CPU=<cpus> adds systemReserved.cpu and kubeReserved.cpu to the kind KubeletConfiguration patch. Unset, nothing changes.

Not verified at the density that triggered it. shellcheck clean.

Comment thread hack/create-kind-cluster.sh Resolved
@BenTheElder

Copy link
Copy Markdown
Collaborator

for this and #2643 can we pick a different prefix? KIND_ also refers to some env that kind respects, these are not. e.g. KIND_CLUSTER_NAME is a real builtin to kind. We should use our own prefix for bespoke knobs?

Dense nodes starve the kubelet's heartbeat; after the 300 s toleration the
taint manager evicts the node's pods. Opt-in; unset leaves the config as is.
KIND_ is the environment namespace kind itself reads. The knob is now
listed in --help as well.
@dims Davanum Srinivas (dims) changed the title hack: KIND_RESERVED_CPU reserves kubelet and system CPU on kind nodes hack: ATE_KIND_RESERVED_CPU reserves kubelet and system CPU on kind nodes Oct 15, 2026
@dims

Davanum Srinivas (dims) commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator Author

We should use our own prefix for bespoke knobs?

added ATE_ prefix!

@BenTheElder
Benjamin Elder (BenTheElder) added this pull request to the merge queue Oct 15, 2026
@dims

Copy link
Copy Markdown
Collaborator Author

thanks Benjamin Elder (@BenTheElder)

Merged via the queue into agent-substrate:main with commit 0c2776a Oct 15, 2026
15 checks passed
@BenTheElder

Copy link
Copy Markdown
Collaborator

I plan to get to more of your PRs this afternoon, got into multiple last minute API bikeshed :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants