This is an automated email from the ASF dual-hosted git repository.
wilfreds pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-yunikorn-site.git
The following commit(s) were added to refs/heads/master by this push:
new 21ed723 [YUNIKORN-479] Update 'Deploy to Kubernetes' doc (#32)
21ed723 is described below
commit 21ed7233711aac9cb6219deffe44c1740bb77d7d
Author: Ashik J M <[email protected]>
AuthorDate: Thu Dec 10 13:07:34 2020 +1100
[YUNIKORN-479] Update 'Deploy to Kubernetes' doc (#32)
Inform users to add applicationId label to the pod spec when there is no
admission controller.
Fixes: #32
---
docs/developer_guide/deployment.md | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/docs/developer_guide/deployment.md
b/docs/developer_guide/deployment.md
index a4b4855..57420cf 100644
--- a/docs/developer_guide/deployment.md
+++ b/docs/developer_guide/deployment.md
@@ -97,7 +97,17 @@ 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)
-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.
+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:
+ name: pod_example
+ labels:
+ applicationId: appID
+ spec:
+ schedulerName: yunikorn
+```
+
+Note: Admission controller abstracts the addition of `schedulerName` and
`applicationId` from the user and hence, routes all traffic to YuniKorn. If you
use helm chart to deploy, it will install admission controller along with the
scheduler.
## Access to the web UI
