Updated Readme

Signed-off-by: Lehmann_Fabian <fabian.lehmann@informatik.hu-berlin.de>

Author: Lehmann-Fabian

README.md

@@ -33,6 +33,98 @@ For more details, we refer to the paper.
 
 ---
 
+#### Run on Kubernetes
+You need to create an account to use the Common Workflow Scheduler in Kubernetes.
+Therefore, create a file `account.yaml` with the following content.
+Afterward, apply this to your Kubernetes cluster `kubectl apply -f account.yaml`
+```
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  name: cwsaccount
+
+---
+
+kind: ClusterRole
+apiVersion: rbac.authorization.k8s.io/v1
+metadata:
+  name: cwsrole
+rules:
+ - apiGroups: [""]
+   resources: ["pods","pods/status","pods/exec","nodes","bindings","configmaps"]
+   verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
+ - apiGroups: ["metrics.k8s.io"]
+   resources: ["nodes"]
+   verbs: ["get","list"]
+
+---
+
+kind: ClusterRoleBinding
+apiVersion: rbac.authorization.k8s.io/v1
+metadata:
+   name: cwsbinding
+subjects:
+ - kind: ServiceAccount
+   name: cwsaccount
+   namespace: <your namespace>
+roleRef:
+   kind: ClusterRole
+   name: cwsrole
+   apiGroup: rbac.authorization.k8s.io
+```
+
+Next, you can start the Common Workflow Scheduler in your Kubernetes environment. 
+Nextflow will start the Common Workflow Scheduler automatically.
+Therefore, create a file `cws.yaml` with the following content.
+Afterward, apply this to your Kubernetes cluster `kubectl apply -f cws.yaml`
+
+```
+apiVersion: v1
+kind: Pod
+metadata:
+  labels:
+    app: cws
+    component: scheduler
+    tier: control-plane
+  name: workflow-scheduler
+spec:
+  containers:
+  - env:
+    - name: SCHEDULER_NAME
+      value: workflow-scheduler
+    - name: AUTOCLOSE
+      value: "false"
+    image: commonworkflowscheduler/kubernetesscheduler:v1.0
+    imagePullPolicy: Always
+    name: workflow-scheduler
+    resources:
+      limits:
+        cpu: "2"
+        memory: 1400Mi
+      requests:
+        cpu: "2"
+        memory: 1400Mi
+    volumeMounts:
+    - mountPath: /input # mount at the same path as you do in your workflow
+      name: vol-1
+    - mountPath: /data
+      name: vol-2
+  nodeSelector: 
+    cwsscheduler: 'true'
+  securityContext:
+    runAsUser: 0
+  serviceAccount: cwsaccount # use the account created before
+  volumes:
+  - name: vol-1
+    persistentVolumeClaim:
+      claimName: api-exp-input # mount the same pvc as you use in your workflow.
+  - name: vol-2
+    persistentVolumeClaim:
+      claimName: api-exp-data
+```
+
+---
+
 If you use this software or artifacts in a publication, please cite it as:
 
 #### Text