Kubernetes

The Neo4j Helm charts replace the Labs Helm charts project at https://neo4j.com/labs. This is the recommended way to run Neo4j on Kubernetes. For more information on how to move from the Labs Helm charts to the Neo4j Helm charts, see the Migrate Neo4j from the Labs Helm charts to the Neo4j Helm charts (offline).

This chapter describes the following:

Introduction — Introduction to running Neo4j on a Kubernetes cluster using Neo4j Helm charts.
Configure the Neo4j Helm chart repository — Configure the Neo4j Helm chart repository and check for the available charts.
Quickstart: Deploy a standalone instance — Deploy a Neo4j standalone instance to a cloud (GKE, AWS, AKS) or a local (via Docker Desktop for macOS) Kubernetes cluster.
Quickstart: Deploy a cluster — Deploy a Neo4j cluster to a cloud (GKE, AWS, AKS) Kubernetes cluster.
Volume mounts and persistent volumes — Use persistent volumes with the Neo4j Helm chart and what types Neo4j supports.
Customizing a Neo4j Helm chart — Configure a Neo4j deployment using a customized values.yaml file.
Configuring SSL — Configure SSL for a Neo4j deployment running on Kubernetes.
Authentication and authorization — Configure LDAP and SSO for a Neo4j deployment running on Kubernetes.
Plugins - Configure APOC, Bloom or GDS plugins for a Neo4j deployment running on Kubernetes.
Accessing Neo4j — Access Neo4j running on Kubernetes.
Accessing Neo4j using Kubernetes Ingress — Access Neo4j using Kubernetes Ingress via Reverse-Proxy Helm chart.
Importing data — Import data into a Neo4j database.
Monitoring — Monitor a Neo4j deployment running on Kubernetes.
Operations — Perform operations on a Neo4j deployment running on Kubernetes.
Deploy a single Neo4j cluster across multiple AKS clusters — Deploy a single Neo4j cluster with three primary servers running on three different AKS clusters.
Troubleshooting — Diagnose and troubleshoot a Neo4j deployment running on Kubernetes.