[YUNIKORN-3265] Doc cleanup in yunikorn-site repo

Author: manirajv06

docs/design/scheduler_plugin.md

@@ -21,6 +21,9 @@ title: K8s Scheduler Plugin
 * limitations under the License.
 -->
 
+
+NOTE: The plugin deployment mode is deprecated and no longer supported. Please refer [deployment modes](user_guide/deployment_modes.md) section for more details
+
 ## Background
 
 YuniKorn (on Kubernetes) is traditionally implemented as a ground-up implementation of a Kubernetes scheduler.

docs/developer_guide/build.md

@@ -60,8 +60,7 @@ Building the Docker images can be triggered by following command:
 make image
 ```
 
-This will generate images for the scheduler, scheduler plugin, and admission
-controller.
+This will generate images for the scheduler and admission controller.
 
 The images created can be deployed directly on Kubernetes.
 Some sample deployments that can be used are found under the
@@ -93,7 +92,6 @@ info in the image metadata. You can retrieve this information with docker
 
 ```shell script
 docker inspect apache/yunikorn:scheduler-amd64-latest
-docker inspect apache/yunikorn:scheduler-plugin-amd64-latest
 docker inspect apache/yunikorn:admission-controller-amd64-latest
 ```
 
@@ -229,12 +227,6 @@ make run
 This will launch a local scheduler and connect to the Kubernetes cluster
 referenced in your `KUBECONFIG` or `$HOME/.kube/config`.
 
-To run YuniKorn in Kubernetes scheduler plugin mode instead, execute:
-
-```
-make run_plugin
-```
-
 You can also use the same approach to run the scheduler locally but connecting
 to a remote kubernetes cluster, as long as the `$HOME/.kube/config` file
 is pointing to that remote cluster.

docs/developer_guide/deployment.md

@@ -85,11 +85,6 @@ The deployment will run 2 containers from your pre-built docker images in 1 pod,
 * yunikorn-scheduler-core (yunikorn scheduler core and shim for K8s)
 * yunikorn-scheduler-web (web UI)
 
-Alternatively, the scheduler can be deployed as a K8S scheduler plugin:
-```
-kubectl create -f deployments/scheduler/plugin.yaml
-```
-
 The pod is deployed as a customized scheduler, it will take the responsibility to schedule pods which explicitly specifies `schedulerName: yunikorn` in pod's spec. In addition to the `schedulerName`, you will also have to add a label `applicationId` to the pod.
 ```yaml
   metadata:

docs/developer_guide/env_setup.md

@@ -225,36 +225,6 @@ Set the following values in the dialog (as shown):
 Once the changes are done, click "Apply", then "Debug". You will need to
 set proper breakpoints in order to debug the program.
 
-## Debug the scheduler plugin
-
-The scheduler may also be run in plugin mode. In this mode, the YuniKorn
-scheduler is built on top of the default scheduler and runs as a
-plugin (rather than completely standalone). Functionally, it performs the
-same tasks, but relies on the upstream Kubernetes scheduler codebase for
-common functionality.
-
-The run configuration for the scheduler in plugin mode is as follows:
-
-- Run Kind: Package
-- Package path: `github.com/apache/yunikorn-k8shim/pkg/cmd/schedulerplugin`
-- Working directory: Project base directory (`yunikorn-k8shim`)
-- Program arguments:
-  ```
-  --bind-address=0.0.0.0
-  --leader-elect=false
-  --config=conf/scheduler-config-local.yaml
-  -v=2
-  ```
-- Environment: If `KUBECONFIG` is not set globally, ensure it is set here.
-  Additionally, you may want to set `NAMESPACE=yunikorn`, as otherwise
-  YuniKorn will look for the `yunikorn-configs` ConfigMap under the
-  `default` Kubernetes namespace.
-
-Additionally, before running for the first time, run `make init` from a
-terminal in the root of the `yunikorn-k8shim` repository. This will
-generate the contents of `conf/scheduler-config-local.yaml`, which is
-required.
-
 ## Access remote Kubernetes cluster
 
 This setup assumes you have already installed a remote Kubernetes cluster. 

docs/user_guide/service_config.md

@@ -46,12 +46,6 @@ image:
   tag: scheduler-{version}          # default depends on YuniKorn version
   pullPolicy: Always
 
-# Image information for the plugin scheduler
-pluginImage:
-  repository: apache/yunikorn
-  tag: scheduler-plugin-{version}   # default depends on YuniKorn version
-  pullPolicy: Always
-
 # Image information for the web UI
 web:
   image:
@@ -402,15 +396,7 @@ Example:
 ```yaml
 embedAdmissionController: false
 ```
-#### enableSchedulerPlugin
-Controls whether to run YuniKorn in scheduler plugin mode.
-
-Default: `false`
 
-Example:
-```yaml
-enableSchedulerPlugin: true
-```
 #### enableWebService
 Controls whether to enable the YuniKorn Web UI service.
 
@@ -995,9 +981,8 @@ all pods which are scheduled by YuniKorn will have an `applicationId` label appl
 When running YuniKorn using the standard deployment model, all pods should be labeled,
 as YuniKorn is unable to schedule pods without an `applicationId` defined.
 
-When running YuniKorn using the scheduler plugin deployment model, this setting can
-be used to filter which namespaces should be scheduled via YuniKorn's queueing model,
-and which should bypass queueing and be scheduled by the embedded default scheduler.
+This setting can be used to filter which namespaces should be scheduled via YuniKorn's queueing model,
+and which should bypass queueing and be scheduled by the default scheduler.
 
 This setting is a comma-separated list of regular expressions. If this setting
 is an empty string, all pods forwarded to YuniKorn will have an `applicationId` label
@@ -1019,9 +1004,8 @@ acts as an exception list to `admissionController.filtering.labelNamespaces`.
 When running YuniKorn using the standard deployment model, all pods should be labeled,
 as YuniKorn is unable to schedule pods without an `applicationId` defined.
 
-When running YuniKorn using the scheduler plugin deployment model, this setting can
-be used to filter which namespaces should be scheduled via YuniKorn's queueing model,
-and which should bypass queueing and be scheduled by the embedded default scheduler.
+This setting can be used to filter which namespaces should be scheduled via YuniKorn's queueing model,
+and which should bypass queueing and be scheduled by the default scheduler.
 
 This setting is a comma-separated list of regular expressions. If this setting
 is an empty string, no exclusions to `admissionController.filtering.labelNamespaces` will