Skip to content

use kueue workloads in place of workloads for future workload aware scheduling #8478

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
k8s-ci-robot merged 1 commit into from
Jan 9, 2026
Merged

use kueue workloads in place of workloads for future workload aware scheduling #8478

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion site/content/en/docs/concepts/preemption.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ status:
The `Evicted` condition indicates that the Workload was evicted with a reason `Preempted`,
whereas the `Preempted` condition gives more details about the preemption reason.

The preempting workload can be found by running `kubectl get workloads --selector=kueue.x-k8s.io/job-uid=<JobUID> --all-namespaces`.
The preempting workload can be found by running `kubectl get workloads.kueue.x-k8s.io --selector=kueue.x-k8s.io/job-uid=<JobUID> --all-namespaces`.

## Preemption algorithms

Expand Down
2 changes: 1 addition & 1 deletion site/content/en/docs/tasks/dev/setup_multikueue_tas.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,7 +248,7 @@ Submit a sample job that requires topology-aware scheduling:

```bash
kubectl --context kind-manager apply -f examples/multikueue/dev/sample-tas-job.yaml
kubectl --context kind-manager get workloads -n default
kubectl --context kind-manager get workloads.kueue.x-k8s.io -n default
```

Expected output showing the workload was admitted and delegated to a worker cluster:
Expand Down
6 changes: 3 additions & 3 deletions site/content/en/docs/tasks/manage/setup_object_retention_policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ spec:

```bash
# ~1m after Finished
kubectl get workloads -n default
kubectl get workloads.kueue.x-k8s.io -n default
# <successful-workload not found>
kubectl get jobs -n default
Expand Down Expand Up @@ -184,7 +184,7 @@ spec:

```bash
# ~2m after submission
kubectl get workloads -n default
kubectl get workloads.kueue.x-k8s.io -n default
# NAME QUEUE RESERVED IN ADMITTED FINISHED AGE
# limited-workload False 2m
```
Expand All @@ -193,7 +193,7 @@ kubectl get workloads -n default

```bash
# ~1m after eviction
kubectl get workloads -n default
kubectl get workloads.kueue.x-k8s.io -n default
# <limited-workload not found>
kubectl get jobs -n default
Expand Down
4 changes: 2 additions & 2 deletions site/content/en/docs/tasks/run/jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ Internally, Kueue will create a corresponding [Workload](/docs/concepts/workload
for this Job with a matching name.

```shell
kubectl -n default get workloads
kubectl -n default get workloads.kueue.x-k8s.io
```

The output will be similar to the following:
Expand Down Expand Up @@ -119,7 +119,7 @@ When the ClusterQueue has enough quota to run the Workload, it will admit
the Workload. To see if the Workload was admitted, run the following command:
```shell
kubectl -n default get workloads
kubectl -n default get workloads.kueue.x-k8s.io
```
The output is similar to the following:
Expand Down
2 changes: 1 addition & 1 deletion site/content/en/docs/tasks/run/run_cronjobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Internally, Kueue will create a corresponding [Workload](/docs/concepts/workload
for each run of the Job with a matching name.

```shell
kubectl -n default get workloads
kubectl -n default get workloads.kueue.x-k8s.io
```

The output will be similar to the following:
Expand Down
4 changes: 2 additions & 2 deletions site/content/en/docs/tasks/troubleshooting/troubleshooting_jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ To find the Workload for a Job, you can use any of the following steps:

```bash
JOB_UID=$(kubectl get job -n my-namespace my-job -o jsonpath='{.metadata.uid}')
kubectl get workloads -n my-namespace -l "kueue.x-k8s.io/job-uid=$JOB_UID"
kubectl get workloads.kueue.x-k8s.io -n my-namespace -l "kueue.x-k8s.io/job-uid=$JOB_UID"
```

The output looks like the following:
Expand All @@ -52,7 +52,7 @@ To find the Workload for a Job, you can use any of the following steps:
You can run a command like the following:

```bash
kubectl get workloads -n my-namespace | grep job-my-job
kubectl get workloads.kueue.x-k8s.io -n my-namespace | grep job-my-job
```

The output looks like the following:
Expand Down
2 changes: 1 addition & 1 deletion site/content/zh-CN/docs/concepts/preemption.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ status:
`Evicted` 条件表示该 Workload 因 `Preempted` 原因被驱逐，而 `Preempted` 条件则给出了更多关于抢占原因的细节。

可以通过运行 `kubectl get workloads --selector=kueue.x-k8s.io/job-uid=<JobUID> --all-namespaces` 查找抢占者 workload。
可以通过运行 `kubectl get workloads.kueue.x-k8s.io --selector=kueue.x-k8s.io/job-uid=<JobUID> --all-namespaces` 查找抢占者 workload。

## 抢占算法

Expand Down
6 changes: 3 additions & 3 deletions site/content/zh-CN/docs/tasks/manage/setup_object_retention_policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ spec:

```bash
# ~1m after Finished
kubectl get workloads -n default
kubectl get workloads.kueue.x-k8s.io -n default
# <successful-workload not found>
kubectl get jobs -n default
Expand Down Expand Up @@ -182,7 +182,7 @@ spec:

```bash
# ~2m after submission
kubectl get workloads -n default
kubectl get workloads.kueue.x-k8s.io -n default
# NAME QUEUE RESERVED IN ADMITTED FINISHED AGE
# limited-workload False 2m
```
Expand All @@ -191,7 +191,7 @@ kubectl get workloads -n default

```bash
# ~1m after eviction
kubectl get workloads -n default
kubectl get workloads.kueue.x-k8s.io -n default
# <limited-workload not found>
kubectl get jobs -n default
Expand Down
4 changes: 2 additions & 2 deletions site/content/zh-CN/docs/tasks/run/jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ kubectl create -f sample-job.yaml
在内部，Kueue 将为此 Job 创建一个与名称匹配的相应[Workload](/zh-CN/docs/concepts/workload)。

```shell
kubectl -n default get workloads
kubectl -n default get workloads.kueue.x-k8s.io
```

输出将类似于以下内容：
Expand Down Expand Up @@ -116,7 +116,7 @@ Events: <none>
要查看 Workload 是否被准入，运行以下命令：
```shell
kubectl -n default get workloads
kubectl -n default get workloads.kueue.x-k8s.io
```
输出类似于以下内容：
Expand Down
2 changes: 1 addition & 1 deletion site/content/zh-CN/docs/tasks/run/run_cronjobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ kubectl create -f sample-cronjob.yaml
其名称与 Job 匹配。

```shell
kubectl -n default get workloads
kubectl -n default get workloads.kueue.x-k8s.io
```

输出类似于以下内容：
Expand Down
4 changes: 2 additions & 2 deletions site/content/zh-CN/docs/tasks/troubleshooting/troubleshooting_jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Job 准入的详细信息，无论它是否被准入。

```bash
JOB_UID=$(kubectl get job -n my-namespace my-job -o jsonpath='{.metadata.uid}')
kubectl get workloads -n my-namespace -l "kueue.x-k8s.io/job-uid=$JOB_UID"
kubectl get workloads.kueue.x-k8s.io -n my-namespace -l "kueue.x-k8s.io/job-uid=$JOB_UID"
```

输出如下所示：
Expand All @@ -55,7 +55,7 @@ Job 准入的详细信息，无论它是否被准入。
你可以运行如下命令：

```bash
kubectl get workloads -n my-namespace | grep job-my-job
kubectl get workloads.kueue.x-k8s.io -n my-namespace | grep job-my-job
```

输出如下所示：
Expand Down
2 changes: 1 addition & 1 deletion site/static/examples/multikueue/dev/setup-kind-multikueue-tas.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,7 +192,7 @@ echo "Submit sample job:"
echo " kubectl --context kind-manager apply -f ${SCRIPT_DIR}/sample-tas-job.yaml"
echo ""
echo "Monitor workloads:"
echo " kubectl --context kind-manager get workloads -n default -w"
echo " kubectl --context kind-manager get workloads.kueue.x-k8s.io -n default -w"
echo ""
echo "Cleanup:"
echo " kind delete clusters manager ${WORKER_CLUSTERS}"