image= \ local:// When running shell, you can use cmd kubectl describe pod to check if the information meets expectations. ServiceAccount When use Client mode to api-service to create and watch executor pods. When use Cluster mode to submit application, spark driver pod use serviceAccount to access api-service to create and watch executor pods. In both cases, you need host node’s filesystem into a pod. • emptyDir: an initially empty volume created when a pod is assigned to a node. • nfs: mounts an existing NFS(Network File System) into a pod. • persistentVolumeClaim:

image= \ local:// When running shell, you can use cmd kubectl describe pod to check if the information meets expectations. ServiceAccount When use Client mode to api-service to create and watch executor pods. When use Cluster mode to submit application, spark driver pod use serviceAccount to access api-service to create and watch executor pods. In both cases, you need host node’s filesystem into a pod. • emptyDir: an initially empty volume created when a pod is assigned to a node. • nfs: mounts an existing NFS(Network File System) into a pod. • persistentVolumeClaim:

kyuubi-env.sh.template log4j.properties.template docker Dockerfile kyuubi-configmap.yaml kyuubi-pod.yaml kyuubi-service.yaml extension kyuubi-extension-spark-3-1_2.12-1.3.1-incubating.jar externals kyuubi-server-585d8944c5-m7j5s 1/1 Running 0 30m kyuubi-server-32sdsa1245-2d2sj 1/1 Running 0 30m then, use pod name to get logs: kubectl -n ${namespace_name} logs kyuubi-server-585d8944c5-m7j5s 22 Chapter 6. image= \ local:// When running shell, you can use cmd kubectl describe pod to check if the information meets expectations. ServiceAccount When use Client mode to

kyuubi-env.sh.template log4j.properties.template docker Dockerfile kyuubi-configmap.yaml kyuubi-pod.yaml kyuubi-service.yaml extension kyuubi-extension-spark-3-1_2.12-1.3.1-incubating.jar externals kyuubi-server-585d8944c5-m7j5s 1/1 Running 0 30m kyuubi-server-32sdsa1245-2d2sj 1/1 Running 0 30m then, use pod name to get logs: kubectl -n ${namespace_name} logs kyuubi-server-585d8944c5-m7j5s 22 Chapter 6. image= \ local:// When running shell, you can use cmd kubectl describe pod to check if the information meets expectations. ServiceAccount When use Client mode to

image= \ local:// When running shell, you can use cmd kubectl describe pod to check if the information meets expectations. 2.2.4. ServiceAccount When use Client mode api-service to create and watch executor pods. When use Cluster mode to submit application, spark driver pod use serviceAccount to access api-service to create and watch executor pods. In both cases, you need host node’s filesystem into a pod. emptyDir: an initially empty volume created when a pod is assigned to a node. nfs: mounts an existing NFS(Network File System) into a pod. persistentVolumeClaim: mounts

image= \ local:// When running shell, you can use cmd kubectl describe pod to check if the information meets expectations. 2.2.4. ServiceAccount When use Client mode api-service to create and watch executor pods. When use Cluster mode to submit application, spark driver pod use serviceAccount to access api-service to create and watch executor pods. In both cases, you need host node’s filesystem into a pod. emptyDir: an initially empty volume created when a pod is assigned to a node. nfs: mounts an existing NFS(Network File System) into a pod. persistentVolumeClaim: mounts

log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod.yaml kyuubi-service.yaml externals engines jars licenses logs pid work From top to bottom are: kyuubi-server-585d8944c5-m7j5s 1/1 Running 0 30m kyuubi-server-32sdsa1245-2d2sj 1/1 Running 0 30m then, use pod name to get logs: kubectl -n ${namespace_name} logs kyuubi-server-585d8944c5-m7j5s 6.1. Quick Start to help you deploy Kyuubi. You can deploy single-node Kyuubi through ${KYUUBI_HOME}/docker/kyuubi-pod.yaml or ${KYUUBI_HOME}/ docker/kyuubi-deployment.yaml. Also, you can use ${KYUUBI_HOME}/docker/kyuubi-service

log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod.yaml kyuubi-service.yaml externals engines jars licenses logs pid work From top to bottom are: kyuubi-server-585d8944c5-m7j5s 1/1 Running 0 30m kyuubi-server-32sdsa1245-2d2sj 1/1 Running 0 30m then, use pod name to get logs: kubectl -n ${namespace_name} logs kyuubi-server-585d8944c5-m7j5s 6.1. Quick Start to help you deploy Kyuubi. You can deploy single-node Kyuubi through ${KYUUBI_HOME}/docker/kyuubi-pod.yaml or ${KYUUBI_HOME}/ docker/kyuubi-deployment.yaml. Also, you can use ${KYUUBI_HOME}/docker/kyuubi-service

log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod.yaml kyuubi-service.yaml externals engines jars licenses logs pid work From top to bottom are: kyuubi-server-585d8944c5-m7j5s 1/1 Running 0 30m kyuubi-server-32sdsa1245-2d2sj 1/1 Running 0 30m then, use pod name to get logs: kubectl -n ${namespace_name} logs kyuubi-server-585d8944c5-m7j5s 6.1. Quick Start to help you deploy Kyuubi. You can deploy single-node Kyuubi through ${KYUUBI_HOME}/docker/kyuubi-pod.yaml or ${KYUUBI_HOME}/ docker/kyuubi-deployment.yaml. Also, you can use ${KYUUBI_HOME}/docker/kyuubi-service

log4j.properties.template ├── docker │ ├── Dockerfile │ ├── kyuubi-configmap.yaml │ ├── kyuubi-pod.yaml │ └── kyuubi-service.yaml ├── extension │ └── kyuubi-extension-spark-3-1_2.12-1.3.1-incubating Running 0 30m kyuubi-server-32sdsa1245-2d2sj 1/1 Running 0 30m then, use pod name to get logs: kubectl -n ${namespace_name} logs kyuubi-server-585d8944c5-m7j5s 3. Getting Started image= \ local:// When running shell, you can use cmd kubectl describe pod to check if the information meets expectations. 2.2.4. ServiceAccount When use Client mode