Skip to main content
helm chart · surrealdb

SurrealDB

Helm chart for deploying surrealdb

Latest version
v0.0.4
Chart type
Data source
Requires
Helm 3+

Install

Add the zop.dev chart repository, then install surrealdb into your cluster.

helm repo add zopdev https://helm.zop.dev
helm repo update
helm install my-surrealdb zopdev/surrealdb --version v0.0.4

The SurrealDB Helm chart provides an easy way to deploy SurrealDB, a next-generation database for modern applications, in your Kubernetes cluster. SurrealDB supports SQL-like queries and is highly flexible, scalable, and efficient.


Prerequisites

  • Kubernetes 1.19+
  • Helm 3+

Add Helm Repository

Add the Helm repository by running:

Terminal window
helm repo add zopdev https://helm.zop.dev
helm repo update

For more details, see the Helm Repository Documentation.


Install Helm Chart

To deploy the SurrealDB Helm chart, use the following command:

Terminal window
helm install [RELEASE_NAME] zopdev/surrealdb

Replace [RELEASE_NAME] with your desired release name. Example:

Terminal window
helm install my-surrealdb zopdev/surrealdb

You can override default values during installation by providing a values.yaml file.

Refer to the Helm Install Documentation for further details.


Uninstall Helm Chart

To remove the SurrealDB Helm chart and associated resources, run:

Terminal window
helm uninstall [RELEASE_NAME]

Example:

Terminal window
helm uninstall my-surrealdb

Check the Helm Uninstall Documentation for more information.


Configuration

The following table lists the configurable parameters of the SurrealDB Helm chart:

InputTypeDescriptionDefault
replicaCountintegerNumber of SurrealDB replicas to deploy.1
imagestringDocker image and tag for the SurrealDB container."surrealdb/surrealdb:latest"
resources.requests.cpustringMinimum CPU resources required by the SurrealDB container."100m"
resources.requests.memorystringMinimum memory resources required by the SurrealDB container."256M"
resources.limits.cpustringMaximum CPU resources the SurrealDB container can use."1000m"
resources.limits.memorystringMaximum memory resources the SurrealDB container can use."1Gi"
diskSizestringSize of the persistent volume for SurrealDB data storage."10Gi"
updateStrategy.typestringUpdate strategy for rolling updates."RollingUpdate"
portintegerPort on which SurrealDB listens for incoming connections.8000

Override these values in a values.yaml file or via command-line arguments during installation.


Example values.yaml File

Below is an example configuration for custom installation:

Terminal window
version: v2
# Resource configuration
resources:
requests:
cpu: "100m"
memory: "256M"
limits:
cpu: "1000m"
memory: "1Gi"
# disk size for surrealdb
diskSize: "10Gi"

Use the custom configuration with the following command:

Terminal window
helm install my-surrealdb zopdev/surrealdb -f values.yaml

Features

  • Scalability: Supports horizontal scaling with replica configuration.
  • Resource Control: Fine-grained control over resource limits and requests for optimized performance.
  • Persistent Storage: Configurable disk size to ensure data durability.
  • Rolling Updates: Seamless updates with no downtime using the rolling update strategy.
  • Flexible Port Configuration: Easily specify the port for database connections.

Pod Scheduling

nodeSelector, tolerations and affinity are passed straight through to the pod spec. All three are empty by default and render nothing, so leaving them unset changes nothing for an existing release.

Together they place the workload on a dedicated node pool — the nodeSelector picks the pool, the toleration gets past its taint:

Terminal window
nodeSelector:
workload: stateful
tolerations:
- key: workload
operator: Equal
value: stateful
effect: NoSchedule

affinity takes a full Affinity object and is rendered verbatim.


Contributing

We welcome contributions to improve this Helm chart. Please refer to the CONTRIBUTING.md file for contribution guidelines.


Code of Conduct

To maintain a healthy and collaborative community, please adhere to our Code of Conduct.


License

This project is licensed under the LICENSE. Please review it for terms of use.


Connection Config

  • SURREAL_PORT : Port on which SurrealDB listens for incoming requests.Defaults at 8000.
  • SURREAL_HOST : Hostname or service name for the SurrealDB instance in the cluster.

See it fire on your bill.

Connect an account read-only. The first findings land in minutes.

472 rule families across 353 resource types on 22 platforms. Every threshold, metric, and IAM action is documented on these pages before you grant anything.

472 rule families documented
353 resource types covered
read-only default access level
Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·