Skip to content

feat(control): limit a zone's CPU time - #73

Open
alexandermerritt wants to merge 1 commit into
mainfrom
alexm/cpu-limit
Open

alexandermerritt wants to merge 1 commit into
mainfrom
alexm/cpu-limit

Conversation

@alexandermerritt

@alexandermerritt alexandermerritt commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

part of ENG-172

used by https://github.com/edera-dev/protect/pull/5032

Do not merge yet.

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedNov 18, 2026, 3:50 PM

A zone's vCPU count is a whole number because the guest kernel sees
it, so a client cannot ask for a fraction of a CPU, such as the
250m a Kubernetes pod limit often holds. cpu_limit_millicpus asks
the hypervisor to hold the zone to that share of physical CPU time
instead, whatever its vCPU count.

The field is optional because UpdateZoneResources replaces a zone's
resources as a whole. A client built before the field leaves it
unset, and that has to keep the zone's limit, not remove it.

Signed-off-by: Alexander M. Merritt <[email protected]>
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.

1 participant