Upgrade a standalone Neo4j using Helm chart across 2025-2026 releases

This example demonstrates how to upgrade a standalone Neo4j server between any two releases within the 2025–2026 cycle.

Upgrade a standalone server

Each Helm chart release is tied to a specific Neo4j version via appVersion in the chart’s Chart.yaml. When you upgrade to a new chart version, the default Neo4j image is updated automatically.

  1. Update the Helm repo:

    helm repo update neo4j

  2. Upgrade the Helm release:

    Upgrade both the chart and the Neo4j version by specifying the target chart version:

    helm upgrade <release-name> neo4j/neo4j --version <chart-version> -f values.yaml

    For example, to upgrade to chart’s version 2026.2.2 (which ships with Neo4j 2026.02.2), run the command:

    helm upgrade <release-name> neo4j/neo4j --version 2026.2.2 -f values.yaml

    Alternatively, if you need to use a specific Neo4j image (e.g., from a private registry) independent of the chart’s default, set image.customImage in your values.yaml:

    image:
  customImage: my-registry.example.com/neo4j:2026.02.2

  3. Monitor the rollout:

    kubectl rollout status --watch --timeout=600s statefulset/<release-name>

  4. Verify Neo4j is running:

    kubectl exec <release-name>-0 -- neo4j status

Upgrade Community to Enterprise

helm upgrade <release-name> neo4j/neo4j --reuse-values \
  --set neo4j.edition=enterprise \
  --set neo4j.acceptLicenseAgreement=yes