Dgraph

This Helm chart deploys a Dgraph cluster on Kubernetes, including Dgraph Zero and Dgraph Alpha components. Below is a detailed guide to the configuration options available.

Prerequisites

• Kubernetes 1.18+
• Helm 3.0+

Add Helm Repository

Add the Helm repository by running:

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 dgraph Helm chart, use the following command:

helm install [RELEASE_NAME] zopdev/dgraph

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

helm install my-dgraph zopdev/dgraph

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 dgraph Helm chart and associated resources, run:

helm uninstall [RELEASE_NAME]

Example:

helm uninstall my-dgraph

Check the Helm Uninstall Documentation for more information.

Configuration

The table below outlines the essential configuration options. For a complete list, refer to the values.yaml file.

Helm Chart Configuration

Zero Configuration

Alpha Configuration

Example values.yaml

global:
  image:
    repository: dgraph/dgraph
    tag: v23.0.0
  debug: false
  serviceAccount: default

zero:
  replicas: 3
  resources:
    requests:
      cpu: 250m
      memory: 512Mi
  persistence:
    enabled: true
    storageClass: ""
  service:
    type: ClusterIP
  tls:
    enabled: false

alpha:
  replicas: 3
  resources:
    requests:
      cpu: 500m
      memory: 1Gi
  persistence:
    enabled: true
    storageClass: ""
  acl:
    enabled: false
  encryption:
    enabled: false
  service:
    type: ClusterIP
  tls:
    enabled: false

Features

• Simplifies Dgraph cluster deployment on Kubernetes.
• Configurable Dgraph Zero and Dgraph Alpha replicas.
• Supports TLS, encryption, and ACL for secure deployments.
• Persistent Volume support for data durability.
• Customizable resource requests and limits for scalability.

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.

They apply to both the zero and alpha StatefulSets.

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

nodeSelector:
  workload: stateful

tolerations:
  - key: workload
    operator: Equal
    value: stateful
    effect: NoSchedule

affinity takes a full Affinity object. Note that setting it replaces the chart’s default soft pod-anti-affinity (which spreads replicas across nodes) rather than merging with it — restate the anti-affinity alongside your own rules if you still want it.

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

• DGRAPH_HOST : Hostname or service name for the Dgraph Alpha service.
• DGRAPH_RPC_PORT : Port for gRPC (RPC) connections to Dgraph. Defaults to 9080.
• DGRAPH_HTTP_PORT : HTTP port for Dgraph’s API. Defaults to 8080.