use full path name for workloads to avoid future conflicts

Author: kannon92

site/content/en/docs/concepts/preemption.md

@@ -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
 

site/content/en/docs/tasks/dev/setup_multikueue_tas.md

@@ -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:

site/content/en/docs/tasks/manage/setup_object_retention_policy.md

@@ -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
@@ -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
 ```
@@ -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

site/content/en/docs/tasks/run/jobs.md

@@ -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:
@@ -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:

site/content/en/docs/tasks/run/run_cronjobs.md

@@ -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:

site/content/en/docs/tasks/troubleshooting/troubleshooting_jobs.md

@@ -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:
@@ -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:

site/content/zh-CN/docs/concepts/preemption.md

@@ -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。
 
 ## 抢占算法
 

site/content/zh-CN/docs/tasks/manage/setup_object_retention_policy.md

@@ -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
@@ -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
 ```
@@ -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

site/content/zh-CN/docs/tasks/run/jobs.md

@@ -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
 ```
 
 输出将类似于以下内容：
@@ -116,7 +116,7 @@ Events:               <none>
 要查看 Workload 是否被准入，运行以下命令：
 
 ```shell
-kubectl -n default get workloads
+kubectl -n default get workloads.kueue.x-k8s.io
 ```
 
 输出类似于以下内容：

site/content/zh-CN/docs/tasks/run/run_cronjobs.md

@@ -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
 ```
 
 输出类似于以下内容：