Skip to main content

​
Overview

Nebuly on GCP is deployed on a Google Kubernetes Engine (GKE) cluster provisioned via a Terraform module, with all platform components managed through an official Helm chart. The setup involves two layers:
  • Infrastructure — Terraform provisions GKE, Cloud SQL (PostgreSQL), Google Cloud Storage, Secret Manager, and supporting IAM and networking resources.
  • Platform — the nebuly-platform Helm chart deploys all Nebuly services onto the provisioned cluster, configured using the values produced by Terraform.
A bootstrap Helm chart (bootstrap-gcp) handles GKE-specific dependencies (ingress, Workload Identity, Secret Manager integration, storage classes) and must be installed before the platform chart.

​
Terraform module

Terraform module for provisioning Nebuly Platform resources on GCP. Available on Terraform Registry.

​
Helm chart

The Nebuly Platform Helm chart is the official way to deploy and manage the Nebuly Platform on Kubernetes. It packages all platform components and is configured using the values produced by the Nebuly Terraform module. Available on GHCR.

​
Prerequisites

​
Nebuly Credentials

Before using this Terraform module, ensure that you have your Nebuly credentials ready. These credentials are necessary to activate your installation and should be provided as input via the nebuly_credentials input.

​
Required GCP APIs

Before using this Terraform module, ensure that the following GCP APIs are enabled in your Google Cloud project: You can enable the APIs using either the GCP Console or the gcloud CLI, as explained in the GCP Documentation.

​
Required GCP Quotas

Ensure that your GCP project has the necessary quotas for the following resources over the regions you plan to deploy Nebuly:
  • Name: GPUs (all regions) Min Value: 2
  • Name: NVIDIA L4 GPUs Min Value: 1
For more information on how to check and increase quotas, refer to the GCP Documentation.

​
Quickstart

To get started with installing Nebuly on GCP, follow the steps below. This guide uses the standard configuration provided by the official Nebuly Helm chart. For advanced configurations or support, feel free to reach out via the Nebuly Slack channel or email us at support@nebuly.ai. Additional examples are available:
  • Basic: Minimal setup with default settings.
  • Microsoft SSO: Setup with Microsoft SSO authentication.

​
1. Terraform setup

Import Nebuly into your Terraform root module, provide the necessary variables, and apply the changes. For configuration examples, you can refer to the Examples. Once the Terraform changes are applied, proceed with the next steps to deploy Nebuly on the provisioned Google Kubernetes Engine (GKE) cluster.

​
2. Connect to the GKE Cluster

For connecting to the created GKE cluster, you can follow the steps below. For more information, refer to the GKE Documentation. 
gcloud components install kubectl
  • Install the Install the gke-gcloud-auth-plugin:
gcloud components install gke-gcloud-auth-plugin
  • Fetch the command for retrieving the credentials from the module outputs:
terraform output gke_cluster_get_credentials
  • Run the command you got from the previous step

​
3. Create image pull secret

The auto-generated Helm values use the name defined in the k8s_image_pull_secret_name input variable for the Image Pull Secret. If you prefer a custom name, update either the Terraform variable or your Helm values accordingly. Create a Kubernetes Image Pull Secret for authenticating with your Docker registry and pulling the Nebuly Docker images. Example: 
kubectl create secret generic nebuly-docker-pull \
  -n nebuly \    
  --from-file=.dockerconfigjson=dockerconfig.json \
  --type=kubernetes.io/dockerconfigjson

​
4. Bootstrap GKE cluster

Install the bootstrap Helm chart to set up all the dependencies required for installing the Nebuly Platform Helm chart on GKE. Refer to the chart documentation for all the configuration details. 
helm install nebuly-bootstrap oci://ghcr.io/nebuly-ai/helm-charts/bootstrap-gcp \
  --namespace nebuly-bootstrap \
  --create-namespace

​
5. Create Secret Provider Class

Create a Secret Provider Class to allow GKE to fetch credentials from the provisioned Key Vault.
  • Get the Secret Provider Class YAML definition from the Terraform module outputs: 
    terraform output secret_provider_class
  • Copy the output of the command into a file named secret-provider-class.yaml.
  • Run the following commands to install Nebuly in the Kubernetes namespace nebuly: 
    kubectl create ns nebuly
kubectl apply --server-side -f secret-provider-class.yaml

​
6. Install nebuly-platform chart

Retrieve the auto-generated values from the Terraform outputs and save them to a file named values.yaml: 
terraform output helm_values
Install the Nebuly Platform Helm chart. Refer to the chart documentation for detailed configuration options. 
helm install <your-release-name> oci://ghcr.io/nebuly-ai/helm-charts/nebuly-platform \
  --namespace nebuly \
  -f values.yaml \
  --timeout 45m
ℹ️ During the initial installation of the chart, all required Nebuly LLMs are uploaded to your model registry. This process can take approximately 5 minutes. If the helm install command appears to be stuck, don’t worry: it’s simply waiting for the upload to finish.

​
7. Access Nebuly

Retrieve the external Load Balancer IP address to access the Nebuly Platform: 
kubectl get svc -n nebuly-bootstrap -o jsonpath='{range .items[?(@.status.loadBalancer.ingress)]}{.status.loadBalancer.ingress[0].ip}{"\n"}{end}'
You can then register a DNS A record pointing to the Load Balancer IP address to access Nebuly via the custom domain you provided in the input variable platform_domain.

​
Examples

You can find examples of code that uses this Terraform module in the examples directory.