From 662b08a96f8c31007072830a6986df16f50f767e Mon Sep 17 00:00:00 2001 From: Michael Date: Thu, 17 Oct 2024 12:51:56 +0800 Subject: [PATCH 1/4] [YUNIKORN-2932] Update local dashboard url in Dev Environment Setup --- docs/developer_guide/env_setup.md | 2 +- versioned_docs/version-0.10.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-0.11.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-0.12.1/developer_guide/env_setup.md | 2 +- versioned_docs/version-0.12.2/developer_guide/env_setup.md | 2 +- versioned_docs/version-0.8.0/setup/env_setup.md | 2 +- versioned_docs/version-0.9.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.0.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.1.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.2.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.3.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.4.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.5.0/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.5.1/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.5.2/developer_guide/env_setup.md | 2 +- versioned_docs/version-1.6.0/developer_guide/env_setup.md | 2 +- 16 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/developer_guide/env_setup.md b/docs/developer_guide/env_setup.md index 4fd59a61e0f..ee5b4df8c53 100644 --- a/docs/developer_guide/env_setup.md +++ b/docs/developer_guide/env_setup.md @@ -70,7 +70,7 @@ Dashboard Web UI. The dashboard may be deployed using the following steps: ```shell script kubectl proxy & ``` -3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login). +3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login). ### Access local Kubernetes cluster diff --git a/versioned_docs/version-0.10.0/developer_guide/env_setup.md b/versioned_docs/version-0.10.0/developer_guide/env_setup.md index c45d77e2164..07d8c2450d0 100644 --- a/versioned_docs/version-0.10.0/developer_guide/env_setup.md +++ b/versioned_docs/version-0.10.0/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-0.11.0/developer_guide/env_setup.md b/versioned_docs/version-0.11.0/developer_guide/env_setup.md index c45d77e2164..07d8c2450d0 100644 --- a/versioned_docs/version-0.11.0/developer_guide/env_setup.md +++ b/versioned_docs/version-0.11.0/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-0.12.1/developer_guide/env_setup.md b/versioned_docs/version-0.12.1/developer_guide/env_setup.md index c45d77e2164..07d8c2450d0 100644 --- a/versioned_docs/version-0.12.1/developer_guide/env_setup.md +++ b/versioned_docs/version-0.12.1/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-0.12.2/developer_guide/env_setup.md b/versioned_docs/version-0.12.2/developer_guide/env_setup.md index c45d77e2164..07d8c2450d0 100644 --- a/versioned_docs/version-0.12.2/developer_guide/env_setup.md +++ b/versioned_docs/version-0.12.2/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-0.8.0/setup/env_setup.md b/versioned_docs/version-0.8.0/setup/env_setup.md index c117e1812f6..354261c5634 100644 --- a/versioned_docs/version-0.8.0/setup/env_setup.md +++ b/versioned_docs/version-0.8.0/setup/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-0.9.0/developer_guide/env_setup.md b/versioned_docs/version-0.9.0/developer_guide/env_setup.md index c45d77e2164..07d8c2450d0 100644 --- a/versioned_docs/version-0.9.0/developer_guide/env_setup.md +++ b/versioned_docs/version-0.9.0/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.0.0/developer_guide/env_setup.md b/versioned_docs/version-1.0.0/developer_guide/env_setup.md index c45d77e2164..07d8c2450d0 100644 --- a/versioned_docs/version-1.0.0/developer_guide/env_setup.md +++ b/versioned_docs/version-1.0.0/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.1.0/developer_guide/env_setup.md b/versioned_docs/version-1.1.0/developer_guide/env_setup.md index c45d77e2164..07d8c2450d0 100644 --- a/versioned_docs/version-1.1.0/developer_guide/env_setup.md +++ b/versioned_docs/version-1.1.0/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +1. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.2.0/developer_guide/env_setup.md b/versioned_docs/version-1.2.0/developer_guide/env_setup.md index a10bcbebc71..f6a6e7a0a2d 100644 --- a/versioned_docs/version-1.2.0/developer_guide/env_setup.md +++ b/versioned_docs/version-1.2.0/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -3. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +3. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.3.0/developer_guide/env_setup.md b/versioned_docs/version-1.3.0/developer_guide/env_setup.md index a10bcbebc71..f6a6e7a0a2d 100644 --- a/versioned_docs/version-1.3.0/developer_guide/env_setup.md +++ b/versioned_docs/version-1.3.0/developer_guide/env_setup.md @@ -52,7 +52,7 @@ After setting up the local Kubernetes you need to deploy the dashboard using the ```shell script kubectl proxy & ``` -3. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login) +3. access the dashboard at the following URL: [clickable link](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login) ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.4.0/developer_guide/env_setup.md b/versioned_docs/version-1.4.0/developer_guide/env_setup.md index 18c5bfdaff9..59008b99459 100644 --- a/versioned_docs/version-1.4.0/developer_guide/env_setup.md +++ b/versioned_docs/version-1.4.0/developer_guide/env_setup.md @@ -70,7 +70,7 @@ Dashboard Web UI. The dashboard may be deployed using the following steps: ```shell script kubectl proxy & ``` -3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login). +3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login). ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.5.0/developer_guide/env_setup.md b/versioned_docs/version-1.5.0/developer_guide/env_setup.md index 4fd59a61e0f..ee5b4df8c53 100644 --- a/versioned_docs/version-1.5.0/developer_guide/env_setup.md +++ b/versioned_docs/version-1.5.0/developer_guide/env_setup.md @@ -70,7 +70,7 @@ Dashboard Web UI. The dashboard may be deployed using the following steps: ```shell script kubectl proxy & ``` -3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login). +3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login). ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.5.1/developer_guide/env_setup.md b/versioned_docs/version-1.5.1/developer_guide/env_setup.md index 4fd59a61e0f..ee5b4df8c53 100644 --- a/versioned_docs/version-1.5.1/developer_guide/env_setup.md +++ b/versioned_docs/version-1.5.1/developer_guide/env_setup.md @@ -70,7 +70,7 @@ Dashboard Web UI. The dashboard may be deployed using the following steps: ```shell script kubectl proxy & ``` -3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login). +3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login). ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.5.2/developer_guide/env_setup.md b/versioned_docs/version-1.5.2/developer_guide/env_setup.md index 4fd59a61e0f..ee5b4df8c53 100644 --- a/versioned_docs/version-1.5.2/developer_guide/env_setup.md +++ b/versioned_docs/version-1.5.2/developer_guide/env_setup.md @@ -70,7 +70,7 @@ Dashboard Web UI. The dashboard may be deployed using the following steps: ```shell script kubectl proxy & ``` -3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login). +3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login). ### Access local Kubernetes cluster diff --git a/versioned_docs/version-1.6.0/developer_guide/env_setup.md b/versioned_docs/version-1.6.0/developer_guide/env_setup.md index 4fd59a61e0f..ee5b4df8c53 100644 --- a/versioned_docs/version-1.6.0/developer_guide/env_setup.md +++ b/versioned_docs/version-1.6.0/developer_guide/env_setup.md @@ -70,7 +70,7 @@ Dashboard Web UI. The dashboard may be deployed using the following steps: ```shell script kubectl proxy & ``` -3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login). +3. Access the dashboard [here](http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard-kong-proxy:443/proxy/#/login). ### Access local Kubernetes cluster From 0d1e9e320a3d9c5120a0bf83bc9173bf283945ef Mon Sep 17 00:00:00 2001 From: Michael Date: Mon, 21 Oct 2024 17:39:09 +0800 Subject: [PATCH 2/4] [YUNIKORN-2941] Remove the introduction of plugin mode from the install section of Get Started --- docs/get_started/get_started.md | 7 ------- versioned_docs/version-1.6.0/get_started/get_started.md | 7 ------- 2 files changed, 14 deletions(-) diff --git a/docs/get_started/get_started.md b/docs/get_started/get_started.md index 4044dea917c..4fea77da331 100644 --- a/docs/get_started/get_started.md +++ b/docs/get_started/get_started.md @@ -43,13 +43,6 @@ By default, the helm chart will install the scheduler, web-server and the admiss When `admission-controller` is installed, it simply routes all traffic to YuniKorn. That means the resource scheduling is delegated to YuniKorn. You can disable it by setting `embedAdmissionController` flag to `false` during the helm install. -The YuniKorn scheduler can also be deployed as a Kubernetes scheduler plugin by setting the Helm `enableSchedulerPlugin` -flag to `true`. This will deploy an alternate Docker image which contains YuniKorn compiled together with the default -scheduler. This new mode offers better compatibility with the default Kubernetes scheduler and is suitable for use with the -admission controller delegating all scheduling to YuniKorn. Because this mode is still very new, it is not enabled by default. - -If you are unsure which deployment mode you should use, refer to our [side-by-side comparison](user_guide/deployment_modes). - If you want to use a specific version of YuniKorn, you can add the `--version` flag to the `helm install` command as follows: ```shell script helm install yunikorn yunikorn/yunikorn --namespace yunikorn --version {version} diff --git a/versioned_docs/version-1.6.0/get_started/get_started.md b/versioned_docs/version-1.6.0/get_started/get_started.md index 92a4f9235af..6d5c1e21235 100644 --- a/versioned_docs/version-1.6.0/get_started/get_started.md +++ b/versioned_docs/version-1.6.0/get_started/get_started.md @@ -43,13 +43,6 @@ By default, the helm chart will install the scheduler, web-server and the admiss When `admission-controller` is installed, it simply routes all traffic to YuniKorn. That means the resource scheduling is delegated to YuniKorn. You can disable it by setting `embedAdmissionController` flag to `false` during the helm install. -The YuniKorn scheduler can also be deployed as a Kubernetes scheduler plugin by setting the Helm `enableSchedulerPlugin` -flag to `true`. This will deploy an alternate Docker image which contains YuniKorn compiled together with the default -scheduler. This new mode offers better compatibility with the default Kubernetes scheduler and is suitable for use with the -admission controller delegating all scheduling to YuniKorn. Because this mode is still very new, it is not enabled by default. - -If you are unsure which deployment mode you should use, refer to our [side-by-side comparison](user_guide/deployment_modes). - If you want to use a specific version of YuniKorn, you can add the `--version` flag to the `helm install` command as follows: ```shell script helm install yunikorn yunikorn/yunikorn --namespace yunikorn --version {version} From caab671d686c2b00c5ccbc8c663536683dbda386 Mon Sep 17 00:00:00 2001 From: Michael Date: Tue, 22 Oct 2024 13:25:48 +0800 Subject: [PATCH 3/4] [YUNIKORN-2941] Remove the introduction of plugin mode from the install section of Get Started --- docs/get_started/get_started.md | 11 +++++++++++ .../version-1.6.0/get_started/get_started.md | 11 +++++++++++ 2 files changed, 22 insertions(+) diff --git a/docs/get_started/get_started.md b/docs/get_started/get_started.md index 4fea77da331..118e547b83e 100644 --- a/docs/get_started/get_started.md +++ b/docs/get_started/get_started.md @@ -43,6 +43,17 @@ By default, the helm chart will install the scheduler, web-server and the admiss When `admission-controller` is installed, it simply routes all traffic to YuniKorn. That means the resource scheduling is delegated to YuniKorn. You can disable it by setting `embedAdmissionController` flag to `false` during the helm install. +The YuniKorn scheduler can also be deployed as a Kubernetes scheduler plugin by setting the Helm `enableSchedulerPlugin` +flag to `true`. This will deploy an alternate Docker image which contains YuniKorn compiled together with the default +scheduler. This new mode offers better compatibility with the default Kubernetes scheduler and is suitable for use with the +admission controller delegating all scheduling to YuniKorn. Because this mode is still very new, it is not enabled by default. + +***NOTE:*** **Plugin mode is now deprecated and will be removed in a future release. +It is strongly recommended to use the standard mode instead. +Refer to [plugin mode](user_guide/deployment_modes#plugin-mode) for more details.** + +If you are unsure which deployment mode you should use, refer to our [side-by-side comparison](user_guide/deployment_modes). + If you want to use a specific version of YuniKorn, you can add the `--version` flag to the `helm install` command as follows: ```shell script helm install yunikorn yunikorn/yunikorn --namespace yunikorn --version {version} diff --git a/versioned_docs/version-1.6.0/get_started/get_started.md b/versioned_docs/version-1.6.0/get_started/get_started.md index 6d5c1e21235..e8124e2df63 100644 --- a/versioned_docs/version-1.6.0/get_started/get_started.md +++ b/versioned_docs/version-1.6.0/get_started/get_started.md @@ -43,6 +43,17 @@ By default, the helm chart will install the scheduler, web-server and the admiss When `admission-controller` is installed, it simply routes all traffic to YuniKorn. That means the resource scheduling is delegated to YuniKorn. You can disable it by setting `embedAdmissionController` flag to `false` during the helm install. +The YuniKorn scheduler can also be deployed as a Kubernetes scheduler plugin by setting the Helm `enableSchedulerPlugin` +flag to `true`. This will deploy an alternate Docker image which contains YuniKorn compiled together with the default +scheduler. This new mode offers better compatibility with the default Kubernetes scheduler and is suitable for use with the +admission controller delegating all scheduling to YuniKorn. Because this mode is still very new, it is not enabled by default. + +***NOTE:*** **Plugin mode is now deprecated and will be removed in a future release. +It is strongly recommended to use the standard mode instead. +Refer to [plugin mode](user_guide/deployment_modes#plugin-mode) for more details.** + +If you are unsure which deployment mode you should use, refer to our [side-by-side comparison](user_guide/deployment_modes). + If you want to use a specific version of YuniKorn, you can add the `--version` flag to the `helm install` command as follows: ```shell script helm install yunikorn yunikorn/yunikorn --namespace yunikorn --version {version} From d4fbf6a8e74891159fbeb4e6578d06a0c0024377 Mon Sep 17 00:00:00 2001 From: Michael Date: Fri, 25 Oct 2024 09:52:03 +0800 Subject: [PATCH 4/4] [YUNIKORN-2941] Remove plugin mode from the install section of Getting Started --- docs/get_started/get_started.md | 11 ----------- .../version-1.6.0/get_started/get_started.md | 4 ---- 2 files changed, 15 deletions(-) diff --git a/docs/get_started/get_started.md b/docs/get_started/get_started.md index 118e547b83e..4fea77da331 100644 --- a/docs/get_started/get_started.md +++ b/docs/get_started/get_started.md @@ -43,17 +43,6 @@ By default, the helm chart will install the scheduler, web-server and the admiss When `admission-controller` is installed, it simply routes all traffic to YuniKorn. That means the resource scheduling is delegated to YuniKorn. You can disable it by setting `embedAdmissionController` flag to `false` during the helm install. -The YuniKorn scheduler can also be deployed as a Kubernetes scheduler plugin by setting the Helm `enableSchedulerPlugin` -flag to `true`. This will deploy an alternate Docker image which contains YuniKorn compiled together with the default -scheduler. This new mode offers better compatibility with the default Kubernetes scheduler and is suitable for use with the -admission controller delegating all scheduling to YuniKorn. Because this mode is still very new, it is not enabled by default. - -***NOTE:*** **Plugin mode is now deprecated and will be removed in a future release. -It is strongly recommended to use the standard mode instead. -Refer to [plugin mode](user_guide/deployment_modes#plugin-mode) for more details.** - -If you are unsure which deployment mode you should use, refer to our [side-by-side comparison](user_guide/deployment_modes). - If you want to use a specific version of YuniKorn, you can add the `--version` flag to the `helm install` command as follows: ```shell script helm install yunikorn yunikorn/yunikorn --namespace yunikorn --version {version} diff --git a/versioned_docs/version-1.6.0/get_started/get_started.md b/versioned_docs/version-1.6.0/get_started/get_started.md index e8124e2df63..92a4f9235af 100644 --- a/versioned_docs/version-1.6.0/get_started/get_started.md +++ b/versioned_docs/version-1.6.0/get_started/get_started.md @@ -48,10 +48,6 @@ flag to `true`. This will deploy an alternate Docker image which contains YuniKo scheduler. This new mode offers better compatibility with the default Kubernetes scheduler and is suitable for use with the admission controller delegating all scheduling to YuniKorn. Because this mode is still very new, it is not enabled by default. -***NOTE:*** **Plugin mode is now deprecated and will be removed in a future release. -It is strongly recommended to use the standard mode instead. -Refer to [plugin mode](user_guide/deployment_modes#plugin-mode) for more details.** - If you are unsure which deployment mode you should use, refer to our [side-by-side comparison](user_guide/deployment_modes). If you want to use a specific version of YuniKorn, you can add the `--version` flag to the `helm install` command as follows: