Besides running a database cluster, it might already be sufficient for your project to deploy a single instance. In the following video I’ll explain how to deploy a single core Neo4J instance using Helm to a managed Kubernetes cluster.
I’ll be using a forked and modified version of the official Helm chart, which you can find in this GitHub repository branch.
The shows example Helm chart got rid of the discovery mechanisms which are not required and some other Kubernetes resources, so the resulting deployment is simpler compared to the cluster version I showed previously.
Try it yourself
Similar to the cluster version, you can try this out yourself by deploying on a managed Kubernetes environment. If you need access to a Kubernetes cluster, you can follow this guide to get started on IKS. You will need Helm in version
With that, Kubernetes will provision the resources including the volume claim and your cloud provider will create the persistent volume.
After a while your persistent volumes will be provisioned:
Once that is the case, the single Neo4J pod provided by the stateful set should be up-and-running:
Testing the connection, and running the example coffee beans application is similar to the cluster version. Here, we only have the
core-0 instance available, which is also accessed from the
graphdb-neo4j service, or directly via
port-forward for debugging purposed, as shown previously.
Happy Neo4J graph databasing!
Published on Java Code Geeks with permission by Sebastian Daschner, partner at our JCG program. See the original article here: Deploying a Neo4J single core on managed Kubernetes (Video)
Opinions expressed by Java Code Geeks contributors are their own.