doc: add task page for Topology-Aware Scheduling#11259
Open
nerdeveloper wants to merge 1 commit into
Open
Conversation
Add a dedicated batch-user walkthrough at site/content/en/docs/tasks/run/topology_aware_scheduling.md showing how to run Jobs with the podset-required-topology, podset-preferred-topology, and podset-unconstrained-topology annotations, along with an "Advanced topics" pointer to PodSet grouping, slices, and multi-layer hierarchy on the concepts page. Adds two new example manifests (site/static/examples/tas/sample-job-required.yaml and sample-job-unconstrained.yaml) and reuses the existing sample-job-preferred.yaml. Adds a Batch user entry to the tasks landing index. Addresses kubernetes-sigs#10066.
k8s-ci-robot
added
release-note-none
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nerdeveloper The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
cncf-cla: no
k8s-ci-robot
added
size/L
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind documentation
/area tas
What this PR does / why we need it:
Adds a dedicated batch-user walkthrough at
site/content/en/docs/tasks/run/topology_aware_scheduling.mdshowing how to run Jobs with the three user-facing TAS annotations:kueue.x-k8s.io/podset-required-topology— strict same-domain placement.kueue.x-k8s.io/podset-preferred-topology— best-effort same-domain placement with fallback.kueue.x-k8s.io/podset-unconstrained-topology— minimize fragmentation, no topology constraint.Verified end-to-end on a fresh 9-node TAS-labelled kind cluster (
hack/testing/kind-cluster-tas.yaml) with Kueue v0.17.3 installed from the release manifests. All three example Jobs were admitted, withtopologyAssignmentpopulated on eachWorkload, and pods landed on the expected hosts.Which issue(s) this PR fixes:
Fixes #10066
Special notes for your reviewer:
PodSetSlices and the multi-layer hierarchy were framed in the issue as a "would also be lovely" extension on top of the required/preferred/unconstrained MVP. They are linked from the new "Advanced topics" section but are left for a follow-up PR so this first cut stays focused.
Does this PR introduce a user-facing change?