Review remarks

kubernetes-sigs · Jun 3, 2024 · ae6cb73 · ae6cb73
1 parent db0ba3b
commit ae6cb73
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 2 deletions.
diff --git a/site/content/en/docs/concepts/multikueue.md b/site/content/en/docs/concepts/multikueue.md
@@ -6,8 +6,8 @@ description: >
   Kueue multi cluster job dispatching.
 ---
 
-{{% alert title="Warning" color="warning" %}}
-_Available in Kueue v0.7.0 and later_
+{{% alert title="Note" color="primary" %}}
+Available in Kueue v0.6.0 and newer
 {{% /alert %}}
 
 {{% alert title="Warning" color="warning" %}}

diff --git a/site/content/en/docs/tasks/manage/setup_multikueue.md b/site/content/en/docs/tasks/manage/setup_multikueue.md
@@ -65,6 +65,13 @@ kubectl config use-context manager-cluster
 Enable the `MultiKueue` feature.
 Check the [Installation](/docs/installation/#change-the-feature-gates-configuration) guide for details on feature gate configuration.
 
+{{% alert title="Warning" color="warning" %}}
+Prior to the version 0.7.0 of Kueue, only the JobSet CRDs should be installed in the management cluster. You can do this by running:
+```bash
+kubectl apply --server-side -f https://raw.githubusercontent.com/kubernetes-sigs/jobset/v0.5.1/config/components/crd/bases/jobset.x-k8s.io_jobsets.yaml
+```
+{{% /alert %}}
+
 ### Create worker's Kubeconfig secret
 
 For the next example, having the `worker1` cluster Kubeconfig stored in a file called `worker1.kubeconfig`, you can create the `worker1-secret` secret by running the following command: