5.11. GCP Marketplace#
Starburst Enterprise Presto is available on the Google Cloud Platform Marketplace. It offers a simple and convenient way to get started with SEP running on the Kubernetes.
Further applicable information can be found in the documentation for SEP on the Google Kubernetes Engine.
This user guide provides information on using the operator to deploy SEP and a and eventually a cluster on the GCP Marketplace - Kubernetes Applications.
We recommend you to use the GCP Marketplace UI with Click to Deploy on GKE to deploy the operator. The command line Deploy via command line installation is not supported.
Setting up and deploying Presto to a Google Kubernetes Engine (GKE) cluster using Google Cloud Marketplace is pretty straightforward.
You can get started by simply following the UI instructions in the marketplace.
You can either use an existing GKE cluster or create a new one. If using an existing cluster make sure you have the GKE cluster configured with the appropriate number and type of instances you may need to deploy a Presto cluster. With insufficient resources available in the cluster, the deployed pods may fail to be scheduled. Please refer this documentation for any additional configuration prerequisites for your GKE cluster.
You can also choose to deploy a new cluster with minimal resources and default configuration from the Marketplace offering configuration page. After the Presto operator deploys successfully in this cluster, you have to review the cluster configuration before deploying Presto on it. You need to ensure that the cluster is sufficiently large.
The default values of the configuration in the UI work for most of the cases.
Note the value for the field Secret name for Starburst enterprise
license and configure it using
licenseSecretName in the Kubernetes configuration. Also, if you are
enabling Global Security using Ranger make sure you note down the values
of the admin and service user passwords you provide in the UI for
Once done, you can click on Deploy to install the operator in the cluster. You can track the progress of the deployment in the applications page.
Once the application is successfully deployed, you are now ready to deploy Presto on the cluster. For next steps, you can either refer the Application info from the application page or the Presto deployment documentation.
You can deploy Presto using the cloud shell
or local shell with
kubectl configured to your GKE cluster.
The complete reference for the Presto configuration to apply (
can be found in the Presto resource
If you are enabling global security refer to the Ranger documentation.
Make sure you have
usageMetrics enabled in your Presto configuration. Our
GCP offering relies on the metrics and if disabled, the Presto deployment is
terminated after 36 hours. Additionally, if using any Starburst extensions
and plugins, the name of the Starburst license
secret from the marketplace UI needs to be configured with the
For example, create a configuration
apiVersion: starburstdata.com/v1 kind: Presto metadata: name: example-presto spec: nameOverride: example-presto licenseSecretName: presto-license service: type: ClusterIP name: example-presto memory: nodeMemoryHeadroom: 1Gi coordinator: cpuRequest: "" memoryAllocation: "" worker: count: 1 prestoWorkerShutdownGracePeriodSeconds: 1 cpuRequest: "" memoryAllocation: "" usageMetrics: enabled: true usageClient: initialDelay: 1m interval: 1m additionalCatalogs: tpcds: | connector.name=tpcds
Configure kubectl to point at your cluster and then apply the configuration:
kubectl apply -f cluster.yaml