Skip to content

docs: document nodegroup resource limits#544

Open
ruanwenjun wants to merge 2 commits into
volcano-sh:masterfrom
ruanwenjun:codex/update-nodegroup-resource-limits-doc
Open

docs: document nodegroup resource limits#544
ruanwenjun wants to merge 2 commits into
volcano-sh:masterfrom
ruanwenjun:codex/update-nodegroup-resource-limits-doc

Conversation

@ruanwenjun

Copy link
Copy Markdown
  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines
  • What kind of change does this PR introduce?

/kind documentation

  • What this PR does / why we need it:

Documents the per-queue, per-nodegroup resource limits introduced by volcano-sh/volcano#5461.

  • Adds the volcano.sh/nodegroup-resource-limits annotation format and a complete Queue example.
  • Explains limit enforcement, fallback scheduling, explicit resource dimensions, absent annotation behavior, and hierarchical Queue semantics.
  • Updates both the English guide and the current Simplified Chinese translation.

Validation:

  • git diff --check
  • npm run build
  • Which issue(s) this PR fixes:

Related to volcano-sh/volcano#5461

@volcano-sh-bot volcano-sh-bot added the kind/documentation Categorizes issue or PR as related to documentation. label Jul 14, 2026
@volcano-sh-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign william-wang for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@volcano-sh-bot

Copy link
Copy Markdown
Collaborator

Welcome @ruanwenjun! It looks like this is your first PR to volcano-sh/website 🎉

@volcano-sh-bot volcano-sh-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 14, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds documentation in both English and Chinese explaining how to configure queue resource limits for each nodegroup using the volcano.sh/nodegroup-resource-limits annotation. The review feedback suggests minor phrasing improvements in both language versions to enhance precision and clarity, such as using 'the amount of resources' instead of 'how many resources' and 'resulting resource usage' instead of 'future usage' to better match the provided formula.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.


### Configure queue resource limits for each nodegroup

Use the `volcano.sh/nodegroup-resource-limits` annotation to limit how many resources a queue can allocate from each nodegroup.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using 'the amount of resources' is more idiomatic and precise than 'how many resources' when referring to continuous resource dimensions like CPU and memory.

Suggested change
Use the `volcano.sh/nodegroup-resource-limits` annotation to limit how many resources a queue can allocate from each nodegroup.
Use the `volcano.sh/nodegroup-resource-limits` annotation to limit the amount of resources a queue can allocate from each nodegroup.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in b5401ab to use “the amount of resources” for clearer and more idiomatic wording.

allocated(Q, G) + task request <= limit(Q, G)
```

If the future usage exceeds the configured limit, the node is rejected for that task. Other allowed nodegroups remain schedulable, so the queue can prefer `groupname1` and overflow to `groupname2` when the logical limit for `groupname1` is reached.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The term 'future usage' is somewhat ambiguous. It would be clearer and more precise to describe it as 'resulting resource usage' or 'total resource usage (allocated resources plus the task's request)' to match the formula allocated(Q, G) + task request <= limit(Q, G) shown above.

Suggested change
If the future usage exceeds the configured limit, the node is rejected for that task. Other allowed nodegroups remain schedulable, so the queue can prefer `groupname1` and overflow to `groupname2` when the logical limit for `groupname1` is reached.
If the resulting resource usage exceeds the configured limit, the node is rejected for that task. Other allowed nodegroups remain schedulable, so the queue can prefer `groupname1` and overflow to `groupname2` when the logical limit for `groupname1` is reached.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in b5401ab to use “resulting resource usage”, matching the allocation formula above.


### 为每个 NodeGroup 配置 Queue 资源上限

使用 `volcano.sh/nodegroup-resource-limits` 注解限制 Queue 最多可从各个 NodeGroup 分配多少资源。

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using '分配的资源量' (the amount of resources allocated) is more idiomatic and precise than '分配多少资源' (how many resources allocated) for resource dimensions like CPU and memory.

Suggested change
使用 `volcano.sh/nodegroup-resource-limits` 注解限制 Queue 最多可从各个 NodeGroup 分配多少资源
使用 `volcano.sh/nodegroup-resource-limits` 注解限制 Queue 最多可从各个 NodeGroup 分配的资源量

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in b5401ab to use “分配的资源量” for more precise Chinese wording.

allocated(Q, G) + task request <= limit(Q, G)
```

如果调度后的资源用量超过配置的上限,插件会拒绝将该任务调度到此节点。其他允许使用的 NodeGroup 仍可参与调度,因此 Queue 可以优先使用 `groupname1`,并在达到 `groupname1` 的逻辑资源上限后将任务调度到 `groupname2`。

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To make the explanation more precise and align with the formula allocated(Q, G) + task request <= limit(Q, G), we can refine '调度后的资源用量' (resource usage after scheduling) to '调度后的累计资源用量' (accumulated resource usage after scheduling).

Suggested change
如果调度后的资源用量超过配置的上限,插件会拒绝将该任务调度到此节点。其他允许使用的 NodeGroup 仍可参与调度,因此 Queue 可以优先使用 `groupname1`,并在达到 `groupname1` 的逻辑资源上限后将任务调度到 `groupname2`
如果调度后的累计资源用量超过配置的上限,插件会拒绝将该任务调度到此节点。其他允许使用的 NodeGroup 仍可参与调度,因此 Queue 可以优先使用 `groupname1`,并在达到 `groupname1` 的逻辑资源上限后将任务调度到 `groupname2`

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in b5401ab to use “调度后的累计资源用量”, aligning the description with the allocation formula.

@yashisrani

Copy link
Copy Markdown
Contributor

/cc @JesseStutler

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

Labels

kind/documentation Categorizes issue or PR as related to documentation. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants