Skip to content

Commit 32ffa21

Browse files
committed
Update docs.
1 parent c6f2083 commit 32ffa21

File tree

2 files changed

+30
-30
lines changed

2 files changed

+30
-30
lines changed

site/content/en/docs/tasks/manage/monitor_pending_workloads/pending_workloads_on_demand.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ kubectl apply -f https://kueue.sigs.k8s.io/examples/visibility/cluster-role-and-
7272

7373
You can disable it by setting the `VisibilityOnDemand` feature gate. Check the [Installation](/docs/installation/#change-the-feature-gates-configuration) guide for details on feature gate configuration.
7474

75-
If you disable the feature, you also need to remove the associated `APIService` from your cluster by doing `kubectl delete APIService v1beta1.visibility.kueue.x-k8s.io`.
75+
If you disable the feature, you also need to remove the associated `APIService` from your cluster by doing `kubectl delete APIService v1beta2.visibility.kueue.x-k8s.io`.
7676

7777
{{% /alert %}}
7878

@@ -103,15 +103,15 @@ for i in {1..6}; do kubectl create -f https://kueue.sigs.k8s.io/examples/jobs/sa
103103
To view pending workloads in ClusterQueue `cluster-queue` run the following command:
104104

105105
```shell
106-
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta1/clusterqueues/cluster-queue/pendingworkloads"
106+
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta2/clusterqueues/cluster-queue/pendingworkloads"
107107
```
108108

109109
You should get results similar to:
110110

111111
```json
112112
{
113113
"kind": "PendingWorkloadsSummary",
114-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
114+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
115115
"metadata": {
116116
"creationTimestamp": null
117117
},
@@ -184,15 +184,15 @@ You can pass optional query parameters:
184184
To view only 1 pending workloads use, starting from position 1 in ClusterQueue run:
185185

186186
```shell
187-
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta1/clusterqueues/cluster-queue/pendingworkloads?limit=1&offset=1"
187+
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta2/clusterqueues/cluster-queue/pendingworkloads?limit=1&offset=1"
188188
```
189189

190190
You should get results similar to
191191

192192
```json
193193
{
194194
"kind": "PendingWorkloadsSummary",
195-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
195+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
196196
"metadata": {
197197
"creationTimestamp": null
198198
},
@@ -226,16 +226,16 @@ If you followed steps described in [Directly accessing the Visibility API](#dire
226226
you can use curl to view pending workloads in ClusterQueue using following commands:
227227

228228
{{< tabpane lang="shell" persist=disabled >}}
229-
{{< tab header="Using kubectl proxy" >}} curl http://localhost:8080/apis/visibility.kueue.x-k8s.io/v1beta1/clusterqueues/cluster-queue/pendingworkloads {{< /tab >}}
230-
{{< tab header="Without kubectl proxy" >}} curl -X GET $APISERVER/apis/visibility.kueue.x-k8s.io/v1beta1/clusterqueues/cluster-queue/pendingworkloads --header "Authorization: Bearer $TOKEN" --insecure {{< /tab >}}
229+
{{< tab header="Using kubectl proxy" >}} curl http://localhost:8080/apis/visibility.kueue.x-k8s.io/v1beta2/clusterqueues/cluster-queue/pendingworkloads {{< /tab >}}
230+
{{< tab header="Without kubectl proxy" >}} curl -X GET $APISERVER/apis/visibility.kueue.x-k8s.io/v1beta2/clusterqueues/cluster-queue/pendingworkloads --header "Authorization: Bearer $TOKEN" --insecure {{< /tab >}}
231231
{{< /tabpane >}}
232232

233233
You should get results similar to:
234234

235235
```json
236236
{
237237
"kind": "PendingWorkloadsSummary",
238-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
238+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
239239
"metadata": {
240240
"creationTimestamp": null
241241
},
@@ -306,15 +306,15 @@ You should get results similar to:
306306
Similarly to ClusterQueue, to view pending workloads in LocalQueue `user-queue` run the following command:
307307

308308
```shell
309-
kubectl get --raw /apis/visibility.kueue.x-k8s.io/v1beta1/namespaces/default/localqueues/user-queue/pendingworkloads
309+
kubectl get --raw /apis/visibility.kueue.x-k8s.io/v1beta2/namespaces/default/localqueues/user-queue/pendingworkloads
310310
```
311311

312312
You should get results similar to:
313313

314314
```json
315315
{
316316
"kind": "PendingWorkloadsSummary",
317-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
317+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
318318
"metadata": {
319319
"creationTimestamp": null
320320
},
@@ -387,15 +387,15 @@ You can pass optional query parameters:
387387
To view only 1 pending workloads use, starting from position 1 in LocalQueue run:
388388

389389
```shell
390-
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta1/namespaces/default/localqueues/user-queue/pendingworkloads?limit=1&offset=1"
390+
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta2/namespaces/default/localqueues/user-queue/pendingworkloads?limit=1&offset=1"
391391

392392
```
393393
You should get results similar to
394394

395395
```json
396396
{
397397
"kind": "PendingWorkloadsSummary",
398-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
398+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
399399
"metadata": {
400400
"creationTimestamp": null
401401
},
@@ -429,16 +429,16 @@ If you followed steps described in [Directly accessing the Visibility API](#dire
429429
above, you can use curl to view pending workloads in LocalQueue using following commands:
430430

431431
{{< tabpane lang="shell" persist=disabled >}}
432-
{{< tab header="Using kubectl proxy" >}} curl http://localhost:8080/apis/visibility.kueue.x-k8s.io/v1beta1/namespaces/default/localqueues/user-queue/pendingworkloads {{< /tab >}}
433-
{{< tab header="Without kubectl proxy" >}} curl -X GET $APISERVER/apis/visibility.kueue.x-k8s.io/v1beta1/namespaces/default/localqueues/user-queue/pendingworkloads --header "Authorization: Bearer $TOKEN" --insecure {{< /tab >}}
432+
{{< tab header="Using kubectl proxy" >}} curl http://localhost:8080/apis/visibility.kueue.x-k8s.io/v1beta2/namespaces/default/localqueues/user-queue/pendingworkloads {{< /tab >}}
433+
{{< tab header="Without kubectl proxy" >}} curl -X GET $APISERVER/apis/visibility.kueue.x-k8s.io/v1beta2/namespaces/default/localqueues/user-queue/pendingworkloads --header "Authorization: Bearer $TOKEN" --insecure {{< /tab >}}
434434
{{< /tabpane >}}
435435

436436
You should get results similar to:
437437

438438
```json
439439
{
440440
"kind": "PendingWorkloadsSummary",
441-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
441+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
442442
"metadata": {
443443
"creationTimestamp": null
444444
},

site/content/zh-CN/docs/tasks/manage/monitor_pending_workloads/pending_workloads_on_demand.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ kubectl apply -f https://kueue.sigs.k8s.io/examples/visibility/cluster-role-and-
7272

7373
You can disable it by setting the `VisibilityOnDemand` feature gate. Check the [Installation](/docs/installation/#change-the-feature-gates-configuration) guide for details on feature gate configuration.
7474

75-
If you disable the feature, you also need to remove the associated `APIService` from your cluster by doing `kubectl delete APIService v1beta1.visibility.kueue.x-k8s.io`.
75+
If you disable the feature, you also need to remove the associated `APIService` from your cluster by doing `kubectl delete APIService v1beta2.visibility.kueue.x-k8s.io`.
7676

7777
{{% /alert %}}
7878

@@ -103,15 +103,15 @@ for i in {1..6}; do kubectl create -f https://kueue.sigs.k8s.io/examples/jobs/sa
103103
To view pending workloads in ClusterQueue `cluster-queue` run the following command:
104104

105105
```shell
106-
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta1/clusterqueues/cluster-queue/pendingworkloads"
106+
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta2/clusterqueues/cluster-queue/pendingworkloads"
107107
```
108108

109109
You should get results similar to:
110110

111111
```json
112112
{
113113
"kind": "PendingWorkloadsSummary",
114-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
114+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
115115
"metadata": {
116116
"creationTimestamp": null
117117
},
@@ -184,15 +184,15 @@ You can pass optional query parameters:
184184
To view only 1 pending workloads use, starting from position 1 in ClusterQueue run:
185185

186186
```shell
187-
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta1/clusterqueues/cluster-queue/pendingworkloads?limit=1&offset=1"
187+
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta2/clusterqueues/cluster-queue/pendingworkloads?limit=1&offset=1"
188188
```
189189

190190
You should get results similar to
191191

192192
```json
193193
{
194194
"kind": "PendingWorkloadsSummary",
195-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
195+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
196196
"metadata": {
197197
"creationTimestamp": null
198198
},
@@ -226,16 +226,16 @@ If you followed steps described in [Directly accessing the Visibility API](#dire
226226
you can use curl to view pending workloads in ClusterQueue using following commands:
227227

228228
{{< tabpane lang="shell" persist=disabled >}}
229-
{{< tab header="Using kubectl proxy" >}} curl http://localhost:8080/apis/visibility.kueue.x-k8s.io/v1beta1/clusterqueues/cluster-queue/pendingworkloads {{< /tab >}}
230-
{{< tab header="Without kubectl proxy" >}} curl -X GET $APISERVER/apis/visibility.kueue.x-k8s.io/v1beta1/clusterqueues/cluster-queue/pendingworkloads --header "Authorization: Bearer $TOKEN" --insecure {{< /tab >}}
229+
{{< tab header="Using kubectl proxy" >}} curl http://localhost:8080/apis/visibility.kueue.x-k8s.io/v1beta2/clusterqueues/cluster-queue/pendingworkloads {{< /tab >}}
230+
{{< tab header="Without kubectl proxy" >}} curl -X GET $APISERVER/apis/visibility.kueue.x-k8s.io/v1beta2/clusterqueues/cluster-queue/pendingworkloads --header "Authorization: Bearer $TOKEN" --insecure {{< /tab >}}
231231
{{< /tabpane >}}
232232

233233
You should get results similar to:
234234

235235
```json
236236
{
237237
"kind": "PendingWorkloadsSummary",
238-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
238+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
239239
"metadata": {
240240
"creationTimestamp": null
241241
},
@@ -306,15 +306,15 @@ You should get results similar to:
306306
Similarly to ClusterQueue, to view pending workloads in LocalQueue `user-queue` run the following command:
307307

308308
```shell
309-
kubectl get --raw /apis/visibility.kueue.x-k8s.io/v1beta1/namespaces/default/localqueues/user-queue/pendingworkloads
309+
kubectl get --raw /apis/visibility.kueue.x-k8s.io/v1beta2/namespaces/default/localqueues/user-queue/pendingworkloads
310310
```
311311

312312
You should get results similar to:
313313

314314
```json
315315
{
316316
"kind": "PendingWorkloadsSummary",
317-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
317+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
318318
"metadata": {
319319
"creationTimestamp": null
320320
},
@@ -387,15 +387,15 @@ You can pass optional query parameters:
387387
To view only 1 pending workloads use, starting from position 1 in LocalQueue run:
388388

389389
```shell
390-
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta1/namespaces/default/localqueues/user-queue/pendingworkloads?limit=1&offset=1"
390+
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1beta2/namespaces/default/localqueues/user-queue/pendingworkloads?limit=1&offset=1"
391391

392392
```
393393
You should get results similar to
394394

395395
```json
396396
{
397397
"kind": "PendingWorkloadsSummary",
398-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
398+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
399399
"metadata": {
400400
"creationTimestamp": null
401401
},
@@ -429,16 +429,16 @@ If you followed steps described in [Directly accessing the Visibility API](#dire
429429
above, you can use curl to view pending workloads in LocalQueue using following commands:
430430

431431
{{< tabpane lang="shell" persist=disabled >}}
432-
{{< tab header="Using kubectl proxy" >}} curl http://localhost:8080/apis/visibility.kueue.x-k8s.io/v1beta1/namespaces/default/localqueues/user-queue/pendingworkloads {{< /tab >}}
433-
{{< tab header="Without kubectl proxy" >}} curl -X GET $APISERVER/apis/visibility.kueue.x-k8s.io/v1beta1/namespaces/default/localqueues/user-queue/pendingworkloads --header "Authorization: Bearer $TOKEN" --insecure {{< /tab >}}
432+
{{< tab header="Using kubectl proxy" >}} curl http://localhost:8080/apis/visibility.kueue.x-k8s.io/v1beta2/namespaces/default/localqueues/user-queue/pendingworkloads {{< /tab >}}
433+
{{< tab header="Without kubectl proxy" >}} curl -X GET $APISERVER/apis/visibility.kueue.x-k8s.io/v1beta2/namespaces/default/localqueues/user-queue/pendingworkloads --header "Authorization: Bearer $TOKEN" --insecure {{< /tab >}}
434434
{{< /tabpane >}}
435435

436436
You should get results similar to:
437437

438438
```json
439439
{
440440
"kind": "PendingWorkloadsSummary",
441-
"apiVersion": "visibility.kueue.x-k8s.io/v1beta1",
441+
"apiVersion": "visibility.kueue.x-k8s.io/v1beta2",
442442
"metadata": {
443443
"creationTimestamp": null
444444
},

0 commit comments

Comments
 (0)