Skip to main content

Deployment

Single-replica deployment still works as before. For multi-replica deployment, see High Availability.
Here is a sample Kubernetes YAML file bytebase.yaml describing the minimal components and configuration required to run Bytebase in Kubernetes.
  1. Start Bytebase with the following command:
  2. Make sure everything worked by listing your deployments:
    Do the same check for your services:

Deploy with Helm

Bytebase provides an official Helm chart for simplified Kubernetes deployments. For comprehensive configuration options and advanced settings, visit the Bytebase Helm Chart on Artifact Hub.
The current official Helm chart deploys a single replica and does not yet expose HA-specific settings such as replica count and the --ha flag. If you want to run Bytebase in HA mode today, use a custom manifest based on this guide or customize the chart template before deploying.

Installation

Deploy Bytebase using Helm with your external PostgreSQL database:
To let the chart construct PG_URL from external PostgreSQL fields, set the host, port, username, database, and authentication-specific values instead of bytebase.option.externalPg.url. For AWS RDS IAM authentication:
For GCP Cloud SQL IAM authentication:
See Configure External PostgreSQL for the required AWS or GCP IAM setup.

Uninstallation

To remove the Bytebase deployment:

HA Deployment

To run Bytebase with multiple replicas on Kubernetes:
  1. Configure an external PostgreSQL database with PG_URL.
  2. Set replicas to more than 1.
  3. Add the --ha flag to every Bytebase replica.
  4. Put the replicas behind one stable ingress, gateway, or service entrypoint.
  5. Make sure the workspace license has HA enabled.
Example: