Using Google Kubernetes Engine#

Google Cloud Platform (GCP), and specifically the Google Kubernetes Engine, is certified to work with SEP.

Online and offline deployments are supported.

GKE-specific tips can be found in this document.

Alternatively you can use the GCP Marketplace version of SEP.

Google Storage Access#

Presto can use Google Storage for data storage. In such cases you need to create a Kubernetes secret with Google Service Account Key and pass it to the Presto Cluster via hive.googleServiceAccountKeySecretName property. For more information on Google Service Account Key secret, refer to Using Google Service Account key.

Network Policy Support#

You need to enable support for Network Policies in Google Kubernetes Engine in order for Presto Network Policies to be effective. For more information, refer to Enabling GKE network policy enforcement.

Accessing Cloud MySQL or PostgreSQL#

In order to access Google Cloud SQL via private IP, you need to start your Kubernetes Cluster with Alias IP addresses. For more information, refer to Creating a Cluster with Alias IP addresses.

Google Service Account Key#

You can provide a Google Service Account Key for the Presto Cluster as a Kubernetes secret. The secret name can be configured using the hive.googleServiceAccountKeySecretName property in the Presto resource.

hive:
  googleServiceAccountKeySecretName: google-service-account-key-secret-name

Such secret should contain single file:

  • key.json

which contains Google Service Account Key in JSON format.

Cluster Autoscaler#

In addition to using the horizontal pod autoscaler, on GKE you can autoscale the number of nodes according to the resources required by pods with the cluster autoscaler. Combined with HPA these two mechanisms allow you to minimize the cost of running an efficient Presto cluster.