Chart version: 1.1.1
Api version: v1
App version: 3.5.17
Neo4j is the world's leading graph database
Chart Type
Set me up:
helm repo add center https://repo.chartcenter.io
Install Chart:
helm install neo4j-community center/equinor-charts/neo4j-community
Versions (0)


> This chart is based on the official neo4j enterprise helm chart, modified to deploy a single-instance neo4j-community deployment. Neo4j is a highly scalable native graph database that leverages data relationships as first-class entities, helping enterprises build intelligent applications to meet today’s evolving data challenges.


bash helm repo add equinor-charts https://equinor.github.io/helm-charts/charts/ helm repo update helm upgrade --install neo4j-community equinor-charts/neo4j-community


This chart bootstraps a Neo4j deployment on a Kubernetes cluster using the Helm package manager.


* Helm 3 * Kubernetes 1.6+ with Beta APIs enabled * PV provisioner support in the underlying infrastructure

Installing the Chart

To install the chart with the release name neo4j-community: bash helm upgrade --install neo4j-community equinor-charts/neo4j-community --set acceptLicenseAgreement=yes --set neo4jPassword=mySecretPassword You must explicitly accept the neo4j license agreement for the installation to be successful. The command deploys Neo4j on the Kubernetes cluster in the default configuration but with the password set to mySecretPassword. The configuration section lists the parameters that can be configured during installation. > Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the neo4j-community deployment: bash helm delete neo4j-community The command removes all the Kubernetes components associated with the chart and deletes the release.


The following table lists the configurable parameters of the Neo4j chart and their default values. | Parameter | Description | Default | | ————————————- | ————————————————————————————————————————————— | ———————————————– | | image | Neo4j image | neo4j | | imageTag | Neo4j version | {VERSION} | | imagePullPolicy | Image pull policy | IfNotPresent | | nodeSelector | Pod node selector | {} | | tolerations | Pod tolerations | [] | | affinity | Pod affinity | {} | | authEnabled | Is login/password required? | true | | neo4jPassword | Password to log in the Neo4J database if password is required | (random string of 10 characters) | | persistentVolume.enabled | Whether or not persistence is enabled | true | | persistentVolume.mountPath | Persistent Volume mount root path | /data | | persistentVolume.size | Size of data volume | 10Gi | | persistentVolume.storageClass | Storage class of backing PVC | standard (uses beta storage class annotation) | | persistentVolume.subPath | Subdirectory of the volume to mount | nil | | extraVars | Extra environment variables to set | nil | | sideCarContainers | Sidecar containers to add to the core pod. Example use case is a sidecar which identifies and labels the leader when using the http API | [] | | initContainers | Init containers to add to the core pod. Example use case is a script that installs the APOC library | [] | | resources | Resources required (e.g. CPU, memory) | {} | The above parameters map to the env variables defined in the Neo4j docker image. Specify each parameter using the --set key=value[,key=value] argument to helm install. For example, bash helm upgrade --install neo4j-community equinor-charts/neo4j-community Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example, bash helm upgrade --install neo4j-community -f values.yaml equinor-charts/neo4j-community > Tip: You can use the default values.yaml

Warning: Updating password

I have not found a way of reliably changing the password set with neo4jPassword on an existing helm deployment. The first time the datastore (PV) is used the password is written to disk. Updating the password and running helm upgrade will not change it. Changing in the Secret will not change it. Using neo4j-admin set-initial-password may or may not update the password in the right place. Your best bet is to remove the helm release, the PV and PVC and start over: helm delete neo4j-helm kubectl delete pv <pvname> & kubectl delete pvc datadir-neo4j-helm-neo4j-community-0

Special considerations when using AzureFile storage

If you want to use AzureFile you need to create a StorageClass with the neo4j user uid&gid in mount options: kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: azurefile-neo4j provisioner: kubernetes.io/azure-file reclaimPolicy: Retain mountOptions: - dir_mode=0755 - file_mode=0755 - uid=101 # Allow write access for neo4j - gid=101 # Allow write access for neo4j parameters: skuName: Standard_LRS And use --set persistentVolume.storageClass=azurefile-neo4j when installing the chart.