Red Hat OpenShift deployment guide #
Starburst Enterprise platform (SEP) is available as an operator on OpenShift directly through the Red Hat Marketplace.
Before you get started, here are some things you need:
- Access to an OpenShift cluster with with correctly-sized nodes, using IAM credentials, and with sufficient Elastic IPs
- Previously installed and configured Kubernetes, including access to
- An editor suitable for editing YAML files
- Your SEP license file
Quick start #
After you have signed up through RHM, download the latest OpenShift Container
Platform (OCP) client for your platform from the OpenShift mirror
oc executable into your path, usually
/usr/local/bin. Once this
is done, you are ready to install the operator in OCP4.
Using your administrator login for Red Hat OCP, log in to the OCP web console and click Operators > OperatorHub in the left-hand menu.
Once there, select “Starburst Enterprise” from the Project: drop-down menu, and navigate through the projects to All Items > Big Data > Starburst until you see Starburst Enterprise. Click on that tile, then click the Install button.
When the Create Operator Subscription page appears, select the Starburst project as the specific namespace on the cluster, leave all other options as default, and click Subscribe.
When the operation is complete, you are subscribed to the SEP operator, and it is installed and accessible to you in OCP4.
Getting up and running #
Once you have your operator subscription in place, it’s time to install. There are several steps to getting SEP installed and deployed:
- Installing the SEP cluster
- Installing the Hive Metastore Service (HMS)
You must install the HMS to connect and query any objects storage with the Hive connector. This is typically a core use case for SEP, and then a required step. The HMS is used by SEP to manage the metadata of any objects storage.
Follow these steps to Install Starburst Enterprise Operator via Red Hat Marketplace:
- On the main menu, click Workspace > My Software > Product > Install Operator
- On the Update Channel section, select an option, ‘stable’ or ‘alpha’
- On the ApprovalStrategy section, select either Automatic or Manual, the approval strategy corresponds to how you want to process operator upgrades)
- On the TargetClustersection:
- Click the checkbox next to the clusters where you want to install the Starburst Enterprise Operator
- For each cluster you selected, under** Namespace Scope, on the **Select Scope list, select an option
- Click Install, it may take several minutes for installation to complete
Once installation is complete, the status changes from Installing to Up to date.
When the operator installation is complete, you can proceed to deploy two custom resources:
Just like with installation, there are several steps to configuring Starburst Enterprise:
Each of these steps uses a specific Helm chart
Click on the links for detailed instructions on configuring each of the custom
The following setup steps are required:
- Configure the resource requirements based on your cluster and node sizes
- Update the image repository and tags to use the RedHat registry:
- Starburst Enterprise:
- Starburst Enterprise Init:
- Starburst Enterprise:
Next steps #
Your cluster is now operational! You can now connect to it with your client tools, and start querying your data sources.
Follow these steps to quickly test your deployed cluster:
- Create a route to the default ‘starburst’ service. If you changed the name in
exposesection, use the new name.
- Run the following command using the CLI with the
trino --server <URL from route> --catalog tpch
SHOW SCHEMAS;in the CLI, and you can see a list of schemas available to query with names such as
sf100, and others.
We’ve created an operations guide to get you started with common first steps in cluster operations.
It includes some great advice about starting with a small, initial configuration that is built upon in our cluster sizing and performance video training.
SEP is powerful, enterprise-grade software with many moving parts. As such, if you find you need help troubleshooting, here are some helpful resources:
Q: Once it’s deployed, how do I access my cluster?
Trino CLI command:
./trino --server example-starburst-enterprise.apps.demo.rht-sbu.io --catalog hive
Web UI URL:
Many other client applications can be connected, and used to run queries, created dashboards and more.
Q: I need to make administrative changes that require a shell prompt. How do I get a command line shell prompt in a container within my cluster?
A: On OCP, you’ll get a shell prompt for a pod. To get a shell prompt for a pod, you’ll need the name of the pod you want to work from. To do so, log in to your cluster as per your RHM documentation. For example:
oc login -u kubeadmin -p XXXXX-XXXXX-XXXXX-XXXX https://api.demo.rht-sbu.io:6443
Get the list of running pods:
❯ oc get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES hive-XXXXXXXXX-lhj7l 1/1 Running 0 27m 10.131.2.XX ip-10-0-139-XXX.us-west-2.compute.internal <none> <none> starburst-enterprise-coordinator-example-XXXXXXXXX-4bzrv 1/1 Running 0 27m 10.129.2.XX ip-10-0-153-XXX.us-west-2.compute.internal <none> <none> starburst-enterprise-operator-7c4ff6dd8f-2xxrr 1/1 Running 0 41m 10.131.2.XX ip-10-0-139-XXX.us-west-2.compute.internal <none> <none> starburst-enterprise-worker-example-XXXXXXXXX-522j8 1/1 Running 0 27m 10.131.2.XX ip-10-0-139-XXX.us-west-2.compute.internal <none> <none> starburst-enterprise-worker-example-XXXXXXXXX-kwxhr 1/1 Running 0 27m 10.130.2.XX ip-10-0-162-XXX.us-west-2.compute.internal <none> <none> starburst-enterprise-worker-example-XXXXXXXXX-phlqq 1/1 Running 0 27m 10.129.2.XX ip-10-0-153-XXX.us-west-2.compute.internal <none> <none>
pod name is the first value in a record. Use the
pod name to open a
❯ oc rsh starburst-enterprise-coordinator-example-XXXXXXXXX-4bzrv
A shell prompt will appear. For example, on OCP 4.4:
Q: Is there a way to get a shell prompt through the OCP web console?
A: Yes. Log in to your OCP web console and navigate to Workloads > Pods. Select the pod you want a terminal for, and click the Terminal tab.
Q: I’ve added a new data source. How do I update the configuration to recognize it?
A: Using the making configuration
changes section to edit your YAML configuration,
additionalCatalogs, and add an entry for your new data source. For
example, to add a PostgreSQL data source called
mydatabase: | connector.name=postgresql connection-url=jdbc:postgresql://172.30.XX.64:5432/pgbench connection-user=pgbench connection-password=postgres123
Once your changes are complete, click
Save and then
Reload to deploy
your changes. Note that this restarts the coordinator and all workers on the
cluster, and might take a little while.
Is the information on this page helpful?