Configuration Reference
Reference tables with a list of all configurable parameters and their defaults.
General Configuration
Parameter | Description | Default |
---|---|---|
|
Neo4j image |
|
|
Neo4j version |
(The default matches the release version of the helm chart itself) |
|
Image pull policy |
|
|
Pod disruption budget |
|
|
Is login/password required? |
|
|
Plugins to automatically install. (syntax must be valid JSON array string) Valid plugins listed here |
|
|
The name of the default database to configure in Neo4j (dbms.default_database) |
|
|
Password to log in the Neo4J database if password is required |
(random string of 10 characters) |
|
The name of the kubernetes secret which contains the neo4j password |
(none) |
|
The key in |
|
|
Extra / custom labels to apply to core & replica statefulset pods |
|
|
Extra / custom annotations to apply to core & replica statefulset pods. |
|
|
Whether to create Role & RoleBinding for this chart. |
|
|
Whether to create a ServiceAccount for this chart. |
|
|
Extra / custom annotations to apply to core & replica service account. |
|
|
Custom core & replica service account name. If empty, name will be generated from the chart’s fullname. |
(none) |
|
The SecurityContext for the Neo4j pod(s). |
The default is |
|
The SecurityContext for the Neo4j database container(s). |
The default is |
Neo4j Core Members
Parameter |
Description |
Default |
|
Configmap providing configuration for core cluster members. If not specified, defaults that come with the chart will be used. |
|
|
YAML list of |
|
|
Whether to run in single-server STANDALONE mode. When using standalone mode, core.numberOfServers is ignored and you will only get 1 Neo4j Pod. The remainder of core configuration applies. |
false |
|
Resources required (e.g. CPU, memory) for the core database members |
|
|
Number of machines in CORE mode |
|
|
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 |
|
|
Init containers to add to the core pod. Example use case is a script that installs custom plugins/extensions |
|
|
Whether or not persistence is enabled |
|
|
Storage class of backing PVC |
|
|
Size of data volume |
|
|
Persistent Volume mount root path |
|
|
Subdirectory of the volume to mount |
|
|
Persistent Volume Claim annotations |
|
|
See the "Other Storage" section in the user guide for more information on this option. |
|
|
See the "Other Storage" section in the user guide for more information on this option. |
|
|
Underlying pod termination grace period; permits Neo4j shutting down to properly flush buffers to disk before exiting, avoiding data corruption. |
|
|
Service type |
|
|
Service annotations |
|
|
Custom Service labels |
|
|
List of IP CIDRs allowed access to LB (if |
|
|
Service type |
|
|
Service annotations |
|
|
Custom Service labels |
|
|
List of IP CIDRs allowed access to LB (if |
|
Neo4j Read Replicas
Parameter |
Description |
Default |
|
Configmap providing configuration for RR cluster members. If not specified, defaults that come with the chart will be used. |
|
|
YAML list of |
|
|
Resources required (e.g. CPU, memory) for the read replica database members |
|
|
Number of machines in READ_REPLICA. May not be used with core.standalone=true mode |
|
|
Enable horizontal pod autoscaler |
|
|
Target CPU utilization |
|
|
Min replicas for autoscaling |
|
|
Max replicas for autoscaling |
|
|
Init containers to add to the replica pods. Example use case is a script that installs custom plugins/extensions |
|
|
See |
|
|
See the "Other Storage" section in the user guide for more information on this option. |
|
|
See the "Other Storage" section in the user guide for more information on this option. |
|
|
Underlying pod termination grace period; permits Neo4j shutting down to properly flush buffers to disk before exiting, avoiding data corruption. |
|
|
Service type |
|
|
Service annotations |
|
|
Custom Service labels |
|
|
List of IP CIDRs allowed accessto LB (if |
|
Naming your Deploy
This chart uses the fullnameOverride
convention, to allow you to control the name of resources that get applied to the cluster. By default, when you install a release called mygraph you’ll end up with resources named things like mygraph-neo4j-core
and mygraph-neo4j-replica
which is the release name, app name, and component name.
If you would like to override this, you may specify any of these values:
-
fullnameOverride
-
fullnamePrefix
-
fullnameSuffix
So for example if you set fullnameOverride=graph
and fullnamePrefix=marketing
then you will see the resources deployed named like:
-
marketing-graph-core
-
marketing-graph-replica
(And so on) which would omit both the helm release name, and the app name (neo4j).