Plan your Kubernetes deployment#
Kubernetes support for Starburst Enterprise platform (SEP) allows you to run SEP clusters with additional components.
Review the requirements, supported platforms, and access considerations before you deploy SEP on Kubernetes.
Supported Kubernetes versions#
Starburst supports Kubernetes versions 1.26 through 1.37.
Kubernetes cluster requirements#
In addition to the SEP requirements listed in deployment basics, cluster nodes must meet the following requirements:
64 to 256 GB RAM
16 to 64 cores
x86_64 (AMD64) or AArch64 (ARM64) processor architecture
All nodes must be identical.
Each node is dedicated to one SEP worker or coordinator only.
Nodes are not shared with other applications running in the cluster.
Kubernetes platform services#
SEP is built on a Kubernetes-native architecture. Starburst supports the following platform services if:
You are running a supported Kubernetes version.
Your cluster nodes meet cluster requirements.
You hold an active, paid support contract with the Kubernetes platform vendor.
Starburst Support handles issues with SEP. Issues determined to be part of the underlying Kubernetes platform are routed to the platform vendor and addressed as part of your vendor support agreement.
The supported platform services are:
If the platform you want to use isn’t listed, contact partners@starburstdata.com.
This topic focuses on Kubernetes usage and practice that applies to all services.
Warning
SEP is designed to work with homogenous resource allocation in terms of network, CPU, and memory for all workers. Resource sharing on a node or pod is therefore not recommended. Failure to ensure this setup can result in unpredictable query performance and query processing failures.
A simple and recommended approach for optimal operation is to ensure that each node only hosts one coordinator or worker pod, and nodes and pods are not shared with other applications. SEP performs best with exclusive access to the underlying memory and CPU resources since it uses significant resources on each node.
The recommended approach to achieve this is to use a dedicated cluster or namespace for all SEP nodes. You can read more about this in our cluster design guidelines.
If you operate SEP in a cluster shared with other applications, you must ensure that all nodes have reliable access to the same amount of CPU, memory, and network resources. You can use nodegroups, taints and tolerations, or pod affinity and anti-affinity as well as CPU and memory requests and limits to achieve consistency across nodes. This approach is not recommended, since it is more complex to implement, but can be used by experienced Kubernetes administrators. Contact your account team for assistance if you are required to use this type of deployment.
Scaling requirements#
In your SEP deployment, install the following components:
Automatic scaling adds and removes worker nodes based on demand. This differs from the commonly used horizontal scaling where new pods are started on existing nodes, and is a result of the fact that workers require a full dedicated node. You must ensure that your Kubernetes cluster supports this addition of nodes and has access to the required resources.
Access requirements#
Access to SEP from outside the cluster using the Trino CLI, or any other application, requires the coordinator to be available via HTTPS and a DNS hostname.
This can be achieved with an external load balancer and DNS that terminates HTTPS and reroutes to HTTP requests inside the cluster.
Alternatively, set up a DNS service for your Kubernetes cluster and configure ingress to route the coordinator’s DNS hostname over HTTPS.
Service database requirement#
The SEP backend service is required. You must provide an externally-managed database appropriate to your environment for the service to use.
Installation tool requirements#
In addition, we strongly recommend Octant to simplify cluster workload visualization and management. The Octant Helm plugin can simplify usage further.
Note
Check out our Helm Troubleshooting tips.
Helm chart repository#
The Helm charts and Docker images required for deployment and operation are available in the Starburst Harbor instance at https://harbor.starburstdata.net.
To obtain a customer-specific Harbor account, contact Starburst Support.
To access the Starburst Helm charts data, use the OCI API.
To download a Starburst Helm chart to your cluster, use the following command:
helm pull oci://harbor.starburstdata.net/starburstdata/charts/<chart-name> --version 2026.6.0
To authenticate to the Starburst Harbor registry storage using the OCI API, use the appropriate commands for your operating system.
Note
You must log in before upgrading to a new version of a chart.
Windows PowerShell#
To authenticate with the Harbor registry storage on Windows PowerShell, use the following command:
echo $env:REGISTRY_PASSWORD | helm registry login harbor.starburstdata.net --username $env:REGISTRY_USERNAME --password-stdin
Running the login command successfully returns a Login Succeeded message in your CLI.
To set your registry credentials as environment variables, use the following commands:
$env:REGISTRY_USERNAME = "your-username"
$env:REGISTRY_PASSWORD = "your-password"
To log out, run the following command:
helm registry logout harbor.starburstdata.net
Linux and Mac#
To authenticate with the Harbor registry storage on Linux and Mac, use the following command:
echo $REGISTRY_PASSWORD | helm registry login harbor.starburstdata.net --username $REGISTRY_USERNAME --password-stdin
Running the login command successfully returns a Login Succeeded message in your CLI.
To set your registry credentials as environment variables, use the following commands:
export REGISTRY_USERNAME='your-username'
export REGISTRY_PASSWORD='your-password'
To log out, run the following command:
helm registry logout harbor.starburstdata.net
Docker registry#
The Helm charts reference the Docker registry on Harbor to download the relevant Docker images. You can also use your own Docker registry.
For more information, see Docker images.
License#
To use SEP, you must get a license file from Starburst Support. For information on how to configure your license file, see Adding the license file.
RBAC-enabled clusters#
Kubernetes by default provides the ClusterRole edit. This role includes
all necessary permissions to deploy and work with Helm charts that consist of
common resources. SEP uses one additional custom type through use of the
externalSecrets: node. However, this custom resource definition must be
deployed to the cluster with its own chart. It is only required in specific use
cases, as in this example.