PowerFlex September 2021 H18899 White Paper Abstract This white paper describes the deployment of a SUSE Rancher Kubernetes Cluster on the Dell EMC PowerFlex family and the integration of PowerFlex family offers key value propositions for traditional and cloud-native production workloads, deployment flexibility, linear scalability, predictable high performance, and enterprise-grade resilience offers flexibility to mix and match the storage, compute, and hyperconverged nodes in a dynamic deployment, allowing you to scale storage and compute resources together or independently, one node at a

corresponding engines, such as Spark, and Flink, is no longer necessary. That is, most work related to deployment, runtime optimization, etc., should be done by professionals on the Kyuubi server side. It is suitable to start with kyuubi quickly on you laptop in about 3~5 minutes. Requirements For quick start deployment, we need to prepare the following stuffs: • A client that connects and submits queries to the kyuubi-env.sh.template 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

corresponding engines, such as Spark, and Flink, is no longer necessary. That is, most work related to deployment, runtime optimization, etc., should be done by professionals on the Kyuubi server side. It is suitable to start with kyuubi quickly on you laptop in about 3~5 minutes. Requirements For quick start deployment, we need to prepare the following stuffs: • A client that connects and submits queries to the kyuubi-env.sh.template 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

corresponding engines, such as Spark, and Flink, is no longer necessary. That is, most work related to deployment, runtime optimization, etc., should be done by professionals on the Kyuubi server side. It is suitable to start with kyuubi quickly on you laptop in about 3~5 minutes. Requirements For quick start deployment, we need to prepare the following stuffs: • A client that connects and submits queries to the kyuubi-env.sh.template 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

corresponding engines, such as Spark, and Flink, is no longer necessary. That is, most work related to deployment, runtime optimization, etc., should be done by professionals on the Kyuubi server side. It is suitable to start with kyuubi quickly on you laptop in about 3~5 minutes. Requirements For quick start deployment, we need to prepare the following stuffs: • A client that connects and submits queries to the kyuubi-env.sh.template 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

corresponding engines, such as Spark, and Flink, is no longer necessary. That is, most work related to deployment, runtime optimization, etc., should be done by professionals on the Kyuubi server side. It is suitable to start with kyuubi quickly on you laptop in about 3~5 minutes. Requirements For quick start deployment, we need to prepare the following stuffs: • A client that connects and submits queries to the ServiceAc- countName for Kyuubi pod, which you can find template in ${KYUUBI_HOME}/docker/kyuubi-deployment.yaml or ${KYUUBI_HOME}/docker/kyuubi-pod.yaml. For example, you can create ServiceAccount by following

0-incubating Requirements These are essential components required for Kyuubi to startup. For quick start deployment, the only thing you need is JAVA_HOME being correctly set. The Kyuubi release package you downloaded kyuubi-env.sh.template 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 forked sub-processes, a.k.a. SQL engines. Running Kyuubi As mentioned above, for a quick start deployment, then only you need to be sure is that the below environments are correct: • Java runtime environment

1-incubating Requirements These are essential components required for Kyuubi to startup. For quick start deployment, the only thing you need is JAVA_HOME being correctly set. The Kyuubi release package you downloaded kyuubi-env.sh.template 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 forked sub-processes, a.k.a. SQL engines. Running Kyuubi As mentioned above, for a quick start deployment, then only you need to be sure is that the below environments are correct: • Java runtime environment

2-incubating Requirements These are essential components required for Kyuubi to startup. For quick start deployment, the only thing you need is JAVA_HOME being correctly set. The Kyuubi release package you downloaded kyuubi-env.sh.template 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 forked sub-processes, a.k.a. SQL engines. Running Kyuubi As mentioned above, for a quick start deployment, then only you need to be sure is that the below environments are correct: • Java runtime environment

corresponding engines, such as Spark, and Flink, is no longer necessary. That is, most work related to deployment, runtime optimization, etc., should be done by professionals on the Kyuubi server side. It is suitable to start with kyuubi quickly on you laptop in about 3~5 minutes. Requirements For quick start deployment, we need to prepare the following stuffs: A client that connects and submits queries to the server template ├── docker │ ├── Dockerfile │ ├── helm │ ├── kyuubi-configmap.yaml │ ├── kyuubi-deployment.yaml │ ├── kyuubi-pod.yaml │ └── kyuubi-service.yaml ├── externals │ └── engines ├── jars