Neo4j-helm allows users to deploy multi-node Neo4j Enterprise Causal Clusters to Kubernetes instances, with configuration options for the most common scenarios. It represents a rapid way to get started running the world leading native graph database on top of Kubernetes.
For Neo4j standalone (i.e . excluding Neo4j Causal Cluster) productized Helm charts for are available for Neo4j 4.3 and above.
That is the recommended way to run a standalone Neo4j server in Kubernetes. Full details are in the Kubernetes section of the Neo4j operations manual
This guide is intended only as a supplement to the Neo4j Operations Manual. Neo4j-helm is a docker container based deploy of Neo4j Causal Cluster. All of the information in the Operations Manual applies to its operation, and this guide will focus only on kubernetes-specific concerns.
|In addition to the information in this user guide, a set of slides is available on the deployment architecture and chart structure of this repository. Neo4j Helm Chart Structure|
The versioning of this helm chart will follow Neo4j versions for simplicity.
Version 4.0.X-Y of the helm chart is compatible with Neo4j EE v4.0.*
Version 4.1.X-Y of the helm chart is compatible with Neo4j EE v4.1.*
(and so on)
The charts in the GitHub repository are for Neo4j 4.0 going forward. There are previous available charts for the Neo4j 3.5 series, but there are substantial differences between the two versions. Careful upgrade planning is advised before attempting to upgrade an existing chart.
Consult the upgrade guide and expect that additional configuration of this chart will be necessary.
The source code to neo4j-helm is available under the terms of the Apache License, version 2.0. See the LICENSE.txt file in the source code repository for full terms and conditions.
This documentation is licensed under Creative Commons 4.0
|The documentation version is v1.0.0|
Was this page helpful?