HPE Ezmeral Container Platform
This topic explains the process to deploy Dremio on the HPE Ezmeral Container Platform and connect to data lake storage.
- An existing Kubernetes cluster setup
- Access to CLI with Helm 3 setup
- Local kubectl configured to access your Kubernetes cluster
- Dremio Helm Chart cloned to your Kubernetes cluster
Configuring Helm Chart for HPE Ezmeral
- From your Kubernetes Cluster, navigate to the
values.yamlfile within the Helm Chart directory.
- Review the default properties in
As part of setting up a Dremio cluster on Kubernetes, there are a number of important considerations that we recommend you review before deploying your cluster. Some of these values have an impact on the performance of your cluster and should be adjusted to your needs.
For a complete reference on all the options available in the
values.yaml, see the Values.yaml Reference documentation — this document covers all the available options and provides small code samples for each configuration option.
- For HPE Ezmeral, you will need to change the Service Type in
values.yamlfrom LoadBalancer to NodePort.
Tip: As a best practice, we recommend creating a
values.local.yaml (or equivalently named file) that stores the values that you wish to override as part of your setup of Dremio. This allows you to quickly update to the latest version of the chart by copying the
values.local.yaml across Helm chart updates.
Installing Helm Chart
- Navigate to the directory where Dremio Helm Chart is located.
- Run the following command:
$ helm install <release name> dremio_v2 -f <pathway>/values.yaml
$ helm install dremio dremio_v2 -f ./dremio_v2/values.yaml --namespace dremio
If you created a
values.local.yaml (or equivalently named file), use that instead of
- Check the status of the installation using the following command:
$ kubectl get pods <pod name>
$ kubectl get pods --namespace dremio
If this process takes more than a couple of minutes to complete, check the status of the pods to see where they are waiting. If they are stuck in the Pending state for an extended period of time, check on the status of the pod to check that there are sufficient resources for scheduling. To check, use the following command on the pending pod:
$ kubectl describe pods <pod name>
$ kubectl describe pods --namespace dremio
If the events at the bottom of the output mention insufficient CPU or memory, either adjust the values in your
values.local.yaml and restart the process or add more resources to your Kubernetes cluster.
- Once you see all the pods in a “ready” state, your setup is all done! See below on how to connect to the Dremio UI to get your first user setup and also how to connect via JDBC/ODBC.
Connection to Dremio User Interface
- Navigate to the HPE Ezmeral Container Platform Console.
- Click Applications on the left navigation pane.
- On the Applications screen, click Service Endpoints.
|Apache Arrow Flight||32010|
- Use the access point associated with the web service to access the UI.
Connecting Dremio to Data Source(s): Dremio supports a variety of data sources, including NoSQL databases, relational databases, Hadoop, local filesystems, and cloud storage.
Connecting Dremio to Client Application: Dremio provides ODBC and JDBC interfaces, supporting a broad range of client applications.