From dd11275327eb9d8cd7f9c722f02a7e18da22041e Mon Sep 17 00:00:00 2001 From: Fazle Rabbi Sarker Date: Tue, 27 Oct 2026 09:17:16 +0000 Subject: [PATCH] Update Neo4j docs to available KubeDB Neo4jVersions Replace the removed 2025.x versions with the versions in the latest KubeDB release (2026.05.0, 2026.06.0, 2026.07.1, 2026.08.1, 5.26.28). Signed-off-by: Fazle Rabbi Sarker --- docs/examples/neo4j/autoscaler/neo4j.yaml | 2 +- .../configuration/neo4j-configuration.yaml | 2 +- .../neo4j/custom-rbac/neo4j-custom-db.yaml | 2 +- .../neo4j/migration/sample-neo4j.yaml | 2 +- .../neo4j/monitoring/builtin-prom-neo4j.yaml | 2 +- .../neo4j/monitoring/coreos-prom-neo4j.yaml | 2 +- .../neo4j/monitoring/neo4j-grafana-demo.yaml | 2 +- .../neo4j/private-registry/pvt-reg-neo4j.yaml | 2 +- docs/examples/neo4j/quickstart/neo4j.yaml | 2 +- .../neo4j/update-version/ops-request.yaml | 2 +- docs/guides/neo4j/README.md | 2 +- .../neo4j/autoscaler/compute/autoscale.md | 4 +-- .../neo4j/autoscaler/storage/autoscale.md | 4 +-- .../customization/common/sample-neo4j.yaml | 2 +- .../examples/remote-neo4j.yaml | 2 +- .../examples/restored-neo4j.yaml | 2 +- .../examples/source-neo4j.yaml | 2 +- .../logical/composite-database/index.md | 8 +++--- .../logical/examples/restored-neo4j.yaml | 2 +- .../logical/examples/sample-neo4j.yaml | 2 +- .../logical/standalone-and-ha/index.md | 18 ++++++------- .../neo4j/clustering/architecture-overview.md | 4 +-- docs/guides/neo4j/concepts/appbinding.md | 2 +- docs/guides/neo4j/concepts/catalog.md | 14 +++++----- docs/guides/neo4j/concepts/neo4j.md | 10 ++++--- docs/guides/neo4j/concepts/opsrequest.md | 2 +- .../neo4j/configuration/using-config-file.md | 4 +-- .../neo4j/custom-rbac/using-custom-rbac.md | 2 +- .../neo4j/migration/storagemigration.md | 4 +-- .../neo4j/monitoring/grafana-dashboard.md | 4 +-- docs/guides/neo4j/monitoring/overview.md | 2 +- .../monitoring/using-builtin-prometheus.md | 4 +-- .../monitoring/using-prometheus-operator.md | 4 +-- .../using-private-registry.md | 12 ++++----- docs/guides/neo4j/quickstart/quickstart.md | 20 +++++++------- .../neo4j/recommendation/recommendation.md | 10 +++---- docs/guides/neo4j/reconfigure/reconfigure.md | 4 +-- docs/guides/neo4j/restart/restart.md | 4 +-- docs/guides/neo4j/rotate-auth/rotateauth.md | 4 +-- .../scale-vertically/index.md | 4 +-- docs/guides/neo4j/tls/configure/index.md | 4 +-- .../update-version/versionupgrading/index.md | 26 +++++++++++-------- .../volume-expansion/volume-expansion.md | 4 +-- 43 files changed, 113 insertions(+), 103 deletions(-) diff --git a/docs/examples/neo4j/autoscaler/neo4j.yaml b/docs/examples/neo4j/autoscaler/neo4j.yaml index 6d671d4b8b..d946a9f9a1 100644 --- a/docs/examples/neo4j/autoscaler/neo4j.yaml +++ b/docs/examples/neo4j/autoscaler/neo4j.yaml @@ -4,7 +4,7 @@ metadata: name: neo4j-autoscale namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: diff --git a/docs/examples/neo4j/configuration/neo4j-configuration.yaml b/docs/examples/neo4j/configuration/neo4j-configuration.yaml index 883e202615..aa384e1642 100644 --- a/docs/examples/neo4j/configuration/neo4j-configuration.yaml +++ b/docs/examples/neo4j/configuration/neo4j-configuration.yaml @@ -4,7 +4,7 @@ metadata: name: custom-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 configuration: secretName: neo4j-configuration diff --git a/docs/examples/neo4j/custom-rbac/neo4j-custom-db.yaml b/docs/examples/neo4j/custom-rbac/neo4j-custom-db.yaml index 621bca8dcd..a3e577d956 100644 --- a/docs/examples/neo4j/custom-rbac/neo4j-custom-db.yaml +++ b/docs/examples/neo4j/custom-rbac/neo4j-custom-db.yaml @@ -4,7 +4,7 @@ metadata: name: quick-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable podTemplate: diff --git a/docs/examples/neo4j/migration/sample-neo4j.yaml b/docs/examples/neo4j/migration/sample-neo4j.yaml index 4c733a52e8..026ef10f6e 100644 --- a/docs/examples/neo4j/migration/sample-neo4j.yaml +++ b/docs/examples/neo4j/migration/sample-neo4j.yaml @@ -6,7 +6,7 @@ metadata: spec: replicas: 3 deletionPolicy: WipeOut - version: "2025.12.1" + version: "2026.08.1" storage: storageClassName: "local-path" accessModes: diff --git a/docs/examples/neo4j/monitoring/builtin-prom-neo4j.yaml b/docs/examples/neo4j/monitoring/builtin-prom-neo4j.yaml index d8f81a3ef3..42f0169f3e 100644 --- a/docs/examples/neo4j/monitoring/builtin-prom-neo4j.yaml +++ b/docs/examples/neo4j/monitoring/builtin-prom-neo4j.yaml @@ -4,7 +4,7 @@ metadata: name: builtin-prom-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 deletionPolicy: WipeOut storage: diff --git a/docs/examples/neo4j/monitoring/coreos-prom-neo4j.yaml b/docs/examples/neo4j/monitoring/coreos-prom-neo4j.yaml index 1053673f87..1c0ea3cfed 100644 --- a/docs/examples/neo4j/monitoring/coreos-prom-neo4j.yaml +++ b/docs/examples/neo4j/monitoring/coreos-prom-neo4j.yaml @@ -6,7 +6,7 @@ metadata: spec: replicas: 3 deletionPolicy: WipeOut - version: "2025.12.1" + version: "2026.08.1" storage: storageClassName: local-path accessModes: diff --git a/docs/examples/neo4j/monitoring/neo4j-grafana-demo.yaml b/docs/examples/neo4j/monitoring/neo4j-grafana-demo.yaml index bdacdaaab0..6c73018ccb 100644 --- a/docs/examples/neo4j/monitoring/neo4j-grafana-demo.yaml +++ b/docs/examples/neo4j/monitoring/neo4j-grafana-demo.yaml @@ -4,7 +4,7 @@ metadata: name: neo4j-grafana-demo namespace: demo spec: - version: "2025.11.2" + version: "2026.08.1" replicas: 3 deletionPolicy: WipeOut storage: diff --git a/docs/examples/neo4j/private-registry/pvt-reg-neo4j.yaml b/docs/examples/neo4j/private-registry/pvt-reg-neo4j.yaml index 00383c2907..b904d75484 100644 --- a/docs/examples/neo4j/private-registry/pvt-reg-neo4j.yaml +++ b/docs/examples/neo4j/private-registry/pvt-reg-neo4j.yaml @@ -4,7 +4,7 @@ metadata: name: pvt-reg-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: diff --git a/docs/examples/neo4j/quickstart/neo4j.yaml b/docs/examples/neo4j/quickstart/neo4j.yaml index e83b38c5fc..43718486d3 100644 --- a/docs/examples/neo4j/quickstart/neo4j.yaml +++ b/docs/examples/neo4j/quickstart/neo4j.yaml @@ -6,7 +6,7 @@ metadata: spec: replicas: 3 deletionPolicy: WipeOut - version: "2025.12.1" + version: "2026.08.1" storage: storageClassName: local-path accessModes: diff --git a/docs/examples/neo4j/update-version/ops-request.yaml b/docs/examples/neo4j/update-version/ops-request.yaml index 84c6e0712f..20e6f0eeeb 100644 --- a/docs/examples/neo4j/update-version/ops-request.yaml +++ b/docs/examples/neo4j/update-version/ops-request.yaml @@ -8,4 +8,4 @@ spec: databaseRef: name: neo4j-test updateVersion: - targetVersion: "2025.12.1" + targetVersion: "2026.08.1" diff --git a/docs/guides/neo4j/README.md b/docs/guides/neo4j/README.md index 3c6398f3d6..341336d171 100644 --- a/docs/guides/neo4j/README.md +++ b/docs/guides/neo4j/README.md @@ -52,7 +52,7 @@ metadata: spec: replicas: 3 deletionPolicy: WipeOut - version: "2025.12.1" + version: "2026.08.1" storage: storageClassName: local-path accessModes: diff --git a/docs/guides/neo4j/autoscaler/compute/autoscale.md b/docs/guides/neo4j/autoscaler/compute/autoscale.md index ad65515b8a..faf6406d80 100644 --- a/docs/guides/neo4j/autoscaler/compute/autoscale.md +++ b/docs/guides/neo4j/autoscaler/compute/autoscale.md @@ -45,7 +45,7 @@ metadata: name: neo4j-autoscale namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: @@ -83,7 +83,7 @@ Wait for the cluster to become ready: ```bash $ kubectl get neo4j -n demo neo4j-autoscale -w NAME VERSION STATUS AGE -neo4j-autoscale 2025.12.1 Ready 3m +neo4j-autoscale 2026.08.1 Ready 3m ``` The Neo4j container initially requests and limits `500m` CPU and `2Gi` memory. Neo4j needs enough memory for the JVM, page cache, and native allocations; limits that are too small can cause the process to be OOM-killed. diff --git a/docs/guides/neo4j/autoscaler/storage/autoscale.md b/docs/guides/neo4j/autoscaler/storage/autoscale.md index ba4f9b373c..731aa673e3 100644 --- a/docs/guides/neo4j/autoscaler/storage/autoscale.md +++ b/docs/guides/neo4j/autoscaler/storage/autoscale.md @@ -55,7 +55,7 @@ metadata: name: neo4j-autoscale namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: @@ -89,7 +89,7 @@ neo4j.kubedb.com/neo4j-autoscale created $ kubectl get neo4j -n demo neo4j-autoscale -w NAME VERSION STATUS AGE -neo4j-autoscale 2025.12.1 Ready 3m +neo4j-autoscale 2026.08.1 Ready 3m ``` Confirm the initial PVC capacities: diff --git a/docs/guides/neo4j/backup/kubestash/customization/common/sample-neo4j.yaml b/docs/guides/neo4j/backup/kubestash/customization/common/sample-neo4j.yaml index 1ba30d69ff..c11b9a1c29 100644 --- a/docs/guides/neo4j/backup/kubestash/customization/common/sample-neo4j.yaml +++ b/docs/guides/neo4j/backup/kubestash/customization/common/sample-neo4j.yaml @@ -4,7 +4,7 @@ metadata: name: sample-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 storageType: Durable storage: diff --git a/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/remote-neo4j.yaml b/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/remote-neo4j.yaml index abe0f9306b..bee01e3573 100644 --- a/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/remote-neo4j.yaml +++ b/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/remote-neo4j.yaml @@ -4,7 +4,7 @@ metadata: name: remote-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 storageType: Durable storage: diff --git a/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/restored-neo4j.yaml b/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/restored-neo4j.yaml index 89c000dc22..12b84bcd70 100644 --- a/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/restored-neo4j.yaml +++ b/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/restored-neo4j.yaml @@ -4,7 +4,7 @@ metadata: name: restored-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 configuration: remoteAliasKeystore: diff --git a/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/source-neo4j.yaml b/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/source-neo4j.yaml index bf8574fa91..31cde39421 100644 --- a/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/source-neo4j.yaml +++ b/docs/guides/neo4j/backup/kubestash/logical/composite-database/examples/source-neo4j.yaml @@ -4,7 +4,7 @@ metadata: name: source-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 configuration: remoteAliasKeystore: diff --git a/docs/guides/neo4j/backup/kubestash/logical/composite-database/index.md b/docs/guides/neo4j/backup/kubestash/logical/composite-database/index.md index 79d80a681c..d0b2cb1e5a 100644 --- a/docs/guides/neo4j/backup/kubestash/logical/composite-database/index.md +++ b/docs/guides/neo4j/backup/kubestash/logical/composite-database/index.md @@ -19,7 +19,7 @@ This guide shows you how to back up and restore physical databases, composite da - Prepare a Kubernetes cluster and configure `kubectl` to access it. - Install [KubeDB](/docs/setup/README.md), [KubeStash](https://kubestash.com/docs/latest/setup/install/kubestash), and the [KubeStash kubectl plugin](https://kubestash.com/docs/latest/setup/install/kubectl-plugin/). -- Use a KubeDB-supported Neo4j Enterprise version that supports composite databases. This guide uses `2025.12.1`. +- Use a KubeDB-supported Neo4j Enterprise version that supports composite databases. This guide uses `2026.08.1`. - Prepare an S3-compatible bucket and its access credentials. - Install a Java Development Kit that provides `keytool` on the machine where you run the setup commands. - Make sure the source and restore-target Neo4j deployments can reach the remote Neo4j Bolt endpoint. @@ -114,7 +114,7 @@ metadata: name: source-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 configuration: remoteAliasKeystore: @@ -150,7 +150,7 @@ metadata: name: remote-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 storageType: Durable storage: @@ -414,7 +414,7 @@ metadata: name: restored-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 configuration: remoteAliasKeystore: diff --git a/docs/guides/neo4j/backup/kubestash/logical/examples/restored-neo4j.yaml b/docs/guides/neo4j/backup/kubestash/logical/examples/restored-neo4j.yaml index 6af8ac8a8b..615f692020 100644 --- a/docs/guides/neo4j/backup/kubestash/logical/examples/restored-neo4j.yaml +++ b/docs/guides/neo4j/backup/kubestash/logical/examples/restored-neo4j.yaml @@ -6,7 +6,7 @@ metadata: spec: init: waitForInitialRestore: true - version: 2025.12.1 + version: 2026.08.1 replicas: 3 storageType: Durable storage: diff --git a/docs/guides/neo4j/backup/kubestash/logical/examples/sample-neo4j.yaml b/docs/guides/neo4j/backup/kubestash/logical/examples/sample-neo4j.yaml index 1ba30d69ff..c11b9a1c29 100644 --- a/docs/guides/neo4j/backup/kubestash/logical/examples/sample-neo4j.yaml +++ b/docs/guides/neo4j/backup/kubestash/logical/examples/sample-neo4j.yaml @@ -4,7 +4,7 @@ metadata: name: sample-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 storageType: Durable storage: diff --git a/docs/guides/neo4j/backup/kubestash/logical/standalone-and-ha/index.md b/docs/guides/neo4j/backup/kubestash/logical/standalone-and-ha/index.md index 6344b6b06c..38fb545a35 100644 --- a/docs/guides/neo4j/backup/kubestash/logical/standalone-and-ha/index.md +++ b/docs/guides/neo4j/backup/kubestash/logical/standalone-and-ha/index.md @@ -67,7 +67,7 @@ metadata: name: sample-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 storageType: Durable storage: @@ -93,7 +93,7 @@ Let's check if the database is ready to use, ```bash $ kubectl get neo4j -n demo sample-neo4j NAME VERSION STATUS AGE -sample-neo4j 2025.12.1 Ready 5m1s +sample-neo4j 2026.08.1 Ready 5m1s ``` The database is `Ready`. Verify that KubeDB has created a `Secret` and a `Service` for this database using the following commands, @@ -120,7 +120,7 @@ Verify that the `AppBinding` has been created successfully using the following c ```bash $ kubectl get appbindings -n demo NAME TYPE VERSION AGE -sample-neo4j kubedb.com/Neo4j 2025.12.1-enterprise 86s +sample-neo4j kubedb.com/Neo4j 2026.08.1-enterprise 86s ``` Let's check the YAML of the above `AppBinding`, @@ -135,7 +135,7 @@ kind: AppBinding metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"Neo4j","metadata":{"annotations":{},"name":"sample-neo4j","namespace":"demo"},"spec":{"deletionPolicy":"WipeOut","replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"2Gi"}}},"storageType":"Durable","version":"2025.12.1"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"Neo4j","metadata":{"annotations":{},"name":"sample-neo4j","namespace":"demo"},"spec":{"deletionPolicy":"WipeOut","replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"2Gi"}}},"storageType":"Durable","version":"2026.08.1"}} creationTimestamp: "2026-06-22T05:50:48Z" generation: 1 labels: @@ -168,7 +168,7 @@ spec: secret: name: sample-neo4j-auth type: kubedb.com/Neo4j - version: 2025.12.1-enterprise + version: 2026.08.1-enterprise ``` KubeStash uses the `AppBinding` CR to connect with the target database. It requires the following fields to be set in the AppBinding's `.spec` section. @@ -452,7 +452,7 @@ apiVersion: storage.kubestash.com/v1alpha1 kind: Snapshot metadata: annotations: - kubedb.com/db-version: 2025.12.1-enterprise + kubedb.com/db-version: 2026.08.1-enterprise creationTimestamp: "2026-06-22T06:11:20Z" finalizers: - kubestash.com/cleanup @@ -550,7 +550,7 @@ metadata: name: restored-neo4j namespace: demo spec: - version: 2025.12.1 + version: 2026.08.1 replicas: 3 storageType: Durable storage: @@ -574,7 +574,7 @@ Let's wait for the database to be ready to use, ```bash $ kubectl get neo4j -n demo restored-neo4j NAME VERSION STATUS AGE -restored-neo4j 2025.12.1 Ready 5m1s +restored-neo4j 2026.08.1 Ready 5m1s ``` The database is `Ready`. Now, we are going to restore the backed up data into this database. @@ -656,7 +656,7 @@ At first, check if the database has gone into **`Ready`** state by the following ```bash $ kubectl get neo4j -n demo restored-neo4j NAME VERSION STATUS AGE -restored-neo4j 2025.12.1 Ready 6m31s +restored-neo4j 2026.08.1 Ready 6m31s ``` Now, find out the database `Pod` by the following command, diff --git a/docs/guides/neo4j/clustering/architecture-overview.md b/docs/guides/neo4j/clustering/architecture-overview.md index e19816493a..80c05baedb 100644 --- a/docs/guides/neo4j/clustering/architecture-overview.md +++ b/docs/guides/neo4j/clustering/architecture-overview.md @@ -89,7 +89,7 @@ metadata: namespace: demo spec: replicas: 3 - version: "2025.12.1" + version: "2026.08.1" storage: storageClassName: local-path accessModes: @@ -114,7 +114,7 @@ When applied: ```bash $ kubectl get neo4j -n demo neo4j-test NAME VERSION STATUS AGE -neo4j-test 2025.12.1 Ready 3m +neo4j-test 2026.08.1 Ready 3m $ kubectl get pods -n demo -l app.kubernetes.io/instance=neo4j-test NAME READY STATUS RESTARTS AGE diff --git a/docs/guides/neo4j/concepts/appbinding.md b/docs/guides/neo4j/concepts/appbinding.md index b82912039a..742476e8df 100644 --- a/docs/guides/neo4j/concepts/appbinding.md +++ b/docs/guides/neo4j/concepts/appbinding.md @@ -51,7 +51,7 @@ spec: secret: name: neo4j-test-auth type: kubedb.com/Neo4j - version: 2025.12.1-enterprise + version: 2026.08.1-enterprise ``` Here, we describe the important sections of this AppBinding. diff --git a/docs/guides/neo4j/concepts/catalog.md b/docs/guides/neo4j/concepts/catalog.md index 3d60ffb084..dd50491382 100644 --- a/docs/guides/neo4j/concepts/catalog.md +++ b/docs/guides/neo4j/concepts/catalog.md @@ -28,13 +28,13 @@ The value of `Neo4j.spec.version` must correspond to a valid `Neo4jVersion` reso apiVersion: catalog.kubedb.com/v1alpha1 kind: Neo4jVersion metadata: - name: 2025.11.2 + name: 2026.08.1 spec: db: - image: docker.io/library/neo4j:2025.11.2-enterprise + image: docker.io/library/neo4j:2026.08.1-enterprise securityContext: runAsUser: 7474 - version: 2025.11.2-enterprise + version: 2026.08.1-enterprise ``` ## Key fields @@ -50,9 +50,11 @@ spec: ```bash $ kubectl get neo4jversions NAME VERSION DB_IMAGE DEPRECATED AGE -2025.10.1 2025.10.1-enterprise docker.io/library/neo4j:2025.10.1-enterprise 12d -2025.11.2 2025.11.2-enterprise docker.io/library/neo4j:2025.11.2-enterprise 12d -2025.12.1 2025.12.1-enterprise docker.io/library/neo4j:2025.12.1-enterprise 12d +2026.05.0 2026.05.0-enterprise docker.io/library/neo4j:2026.05.0-enterprise 14d +2026.06.0 2026.06.0-enterprise docker.io/library/neo4j:2026.06.0-enterprise 14d +2026.07.1 2026.07.1-enterprise docker.io/library/neo4j:2026.07.1-enterprise 14d +2026.08.1 2026.08.1-enterprise docker.io/library/neo4j:2026.08.1-enterprise 14d +5.26.28 5.26.28-enterprise docker.io/library/neo4j:5.26.28-enterprise 14d ``` If the `DEPRECATED` column shows `true` for a version you are currently using, upgrade to a supported version via [UpdateVersion](/docs/guides/neo4j/update-version/versionupgrading/). diff --git a/docs/guides/neo4j/concepts/neo4j.md b/docs/guides/neo4j/concepts/neo4j.md index 488be96a17..9f283a9feb 100644 --- a/docs/guides/neo4j/concepts/neo4j.md +++ b/docs/guides/neo4j/concepts/neo4j.md @@ -31,7 +31,7 @@ metadata: name: neo4j-test namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable configuration: @@ -76,9 +76,11 @@ To see available versions in your cluster: ```bash $ kubectl get neo4jversions NAME VERSION DB_IMAGE DEPRECATED AGE -2025.10.1 2025.10.1-enterprise docker.io/library/neo4j:2025.10.1-enterprise 12d -2025.11.2 2025.11.2-enterprise docker.io/library/neo4j:2025.11.2-enterprise 12d -2025.12.1 2025.12.1-enterprise docker.io/library/neo4j:2025.12.1-enterprise 12d +2026.05.0 2026.05.0-enterprise docker.io/library/neo4j:2026.05.0-enterprise 14d +2026.06.0 2026.06.0-enterprise docker.io/library/neo4j:2026.06.0-enterprise 14d +2026.07.1 2026.07.1-enterprise docker.io/library/neo4j:2026.07.1-enterprise 14d +2026.08.1 2026.08.1-enterprise docker.io/library/neo4j:2026.08.1-enterprise 14d +5.26.28 5.26.28-enterprise docker.io/library/neo4j:5.26.28-enterprise 14d ``` ### spec.replicas diff --git a/docs/guides/neo4j/concepts/opsrequest.md b/docs/guides/neo4j/concepts/opsrequest.md index ce1c2022b5..0bf379f4e3 100644 --- a/docs/guides/neo4j/concepts/opsrequest.md +++ b/docs/guides/neo4j/concepts/opsrequest.md @@ -49,7 +49,7 @@ spec: databaseRef: name: neo4j-test updateVersion: - targetVersion: 2025.12.1 + targetVersion: 2026.08.1 ``` **Sample `Neo4jOpsRequest` for vertical scaling:** diff --git a/docs/guides/neo4j/configuration/using-config-file.md b/docs/guides/neo4j/configuration/using-config-file.md index 8cbb8c3bdb..bab3f571bd 100644 --- a/docs/guides/neo4j/configuration/using-config-file.md +++ b/docs/guides/neo4j/configuration/using-config-file.md @@ -86,7 +86,7 @@ metadata: name: custom-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 configuration: secretName: neo4j-configuration @@ -111,7 +111,7 @@ Now, wait for the Neo4j cluster to be ready: ```bash $ kubectl get neo4j -n demo custom-neo4j -w NAME VERSION STATUS AGE -custom-neo4j 2025.12.1 Ready 3m +custom-neo4j 2026.08.1 Ready 3m ``` ## Verify the Applied Configuration diff --git a/docs/guides/neo4j/custom-rbac/using-custom-rbac.md b/docs/guides/neo4j/custom-rbac/using-custom-rbac.md index a15a0e9cd1..7fb6b2e27f 100644 --- a/docs/guides/neo4j/custom-rbac/using-custom-rbac.md +++ b/docs/guides/neo4j/custom-rbac/using-custom-rbac.md @@ -110,7 +110,7 @@ metadata: name: quick-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable podTemplate: diff --git a/docs/guides/neo4j/migration/storagemigration.md b/docs/guides/neo4j/migration/storagemigration.md index d38f340408..6e7ec9c3e2 100644 --- a/docs/guides/neo4j/migration/storagemigration.md +++ b/docs/guides/neo4j/migration/storagemigration.md @@ -70,7 +70,7 @@ metadata: spec: replicas: 3 deletionPolicy: WipeOut - version: "2025.12.1" + version: "2026.08.1" storage: storageClassName: "local-path" accessModes: @@ -83,7 +83,7 @@ neo4j.kubedb.com/neo4j-test created $ kubectl get neo4j,pvc -n demo NAME VERSION STATUS AGE -neo4j.kubedb.com/neo4j-test 2025.12.1 Ready 2m +neo4j.kubedb.com/neo4j-test 2026.08.1 Ready 2m NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE persistentvolumeclaim/data-neo4j-test-0 Bound ... 2Gi RWO local-path 2m diff --git a/docs/guides/neo4j/monitoring/grafana-dashboard.md b/docs/guides/neo4j/monitoring/grafana-dashboard.md index a49bf7977f..841f174d65 100644 --- a/docs/guides/neo4j/monitoring/grafana-dashboard.md +++ b/docs/guides/neo4j/monitoring/grafana-dashboard.md @@ -55,7 +55,7 @@ metadata: name: neo4j-grafana-demo namespace: demo spec: - version: "2025.11.2" + version: "2026.08.1" replicas: 3 deletionPolicy: WipeOut storage: @@ -92,7 +92,7 @@ Wait for it to be `Ready`: ```bash $ kubectl get neo4j -n demo neo4j-grafana-demo NAME VERSION STATUS AGE -neo4j-grafana-demo 2025.11.2 Ready 3m +neo4j-grafana-demo 2026.08.1 Ready 3m ``` KubeDB creates a stats service named `{neo4j-name}-stats` for the exporter: diff --git a/docs/guides/neo4j/monitoring/overview.md b/docs/guides/neo4j/monitoring/overview.md index 63b7f40a63..0ab78ad2e2 100644 --- a/docs/guides/neo4j/monitoring/overview.md +++ b/docs/guides/neo4j/monitoring/overview.md @@ -48,7 +48,7 @@ metadata: name: sample-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 deletionPolicy: WipeOut storage: diff --git a/docs/guides/neo4j/monitoring/using-builtin-prometheus.md b/docs/guides/neo4j/monitoring/using-builtin-prometheus.md index 9a976223a3..1fcc65c37b 100644 --- a/docs/guides/neo4j/monitoring/using-builtin-prometheus.md +++ b/docs/guides/neo4j/monitoring/using-builtin-prometheus.md @@ -47,7 +47,7 @@ metadata: name: builtin-prom-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 deletionPolicy: WipeOut storage: @@ -77,7 +77,7 @@ Now, wait for the database to go into `Ready` state. ```bash $ kubectl get neo4j -n demo builtin-prom-neo4j NAME VERSION STATUS AGE -builtin-prom-neo4j 2025.12.1 Ready 2m +builtin-prom-neo4j 2026.08.1 Ready 2m ``` KubeDB will create a separate stats service with the name `{Neo4j CR name}-stats` for monitoring purposes. diff --git a/docs/guides/neo4j/monitoring/using-prometheus-operator.md b/docs/guides/neo4j/monitoring/using-prometheus-operator.md index 6e513f1133..0a5d997594 100644 --- a/docs/guides/neo4j/monitoring/using-prometheus-operator.md +++ b/docs/guides/neo4j/monitoring/using-prometheus-operator.md @@ -157,7 +157,7 @@ metadata: spec: replicas: 3 deletionPolicy: WipeOut - version: "2025.12.1" + version: "2026.08.1" storage: storageClassName: local-path accessModes: @@ -192,7 +192,7 @@ Now, wait for the database to go into `Ready` state. ```bash $ kubectl get neo4j -n demo coreos-prom-neo4j NAME VERSION STATUS AGE -coreos-prom-neo4j 2025.12.1 Ready 3m +coreos-prom-neo4j 2026.08.1 Ready 3m ``` KubeDB will create a separate stats service with the name `{Neo4j CR name}-stats` for monitoring purposes. diff --git a/docs/guides/neo4j/private-registry/using-private-registry.md b/docs/guides/neo4j/private-registry/using-private-registry.md index b7a2619cf0..650e0b710e 100644 --- a/docs/guides/neo4j/private-registry/using-private-registry.md +++ b/docs/guides/neo4j/private-registry/using-private-registry.md @@ -34,7 +34,7 @@ namespace/demo created ```bash $ kubectl get neo4jversions -o=custom-columns=NAME:.metadata.name,VERSION:.spec.version,DB_IMAGE:.spec.db.image,DEPRECATED:.spec.deprecated NAME VERSION DB_IMAGE DEPRECATED - 2025.12.1 2025.12.1 kubedb/neo4j:2025.12.1 + 2026.08.1 2026.08.1 kubedb/neo4j:2026.08.1 ``` ## Create ImagePullSecret @@ -62,16 +62,16 @@ Create a Neo4jVersion CRD specifying images from your private registry. Replace apiVersion: catalog.kubedb.com/v1alpha1 kind: Neo4jVersion metadata: - name: "2025.12.1" + name: "2026.08.1" spec: db: - image: PRIVATE_REGISTRY/neo4j:2025.12.1 - version: "2025.12.1" + image: PRIVATE_REGISTRY/neo4j:2026.08.1 + version: "2026.08.1" ``` ```bash $ kubectl apply -f pvt-neo4jversion.yaml -neo4jversion.catalog.kubedb.com/2025.12.1 created +neo4jversion.catalog.kubedb.com/2026.08.1 created ``` ## Deploy Neo4j from Private Registry @@ -83,7 +83,7 @@ metadata: name: pvt-reg-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: diff --git a/docs/guides/neo4j/quickstart/quickstart.md b/docs/guides/neo4j/quickstart/quickstart.md index 586b6a98cb..83ae1e6c93 100644 --- a/docs/guides/neo4j/quickstart/quickstart.md +++ b/docs/guides/neo4j/quickstart/quickstart.md @@ -54,12 +54,14 @@ When KubeDB is installed, it creates `Neo4jVersion` CRDs for all supported Neo4j ```bash $ kubectl get neo4jversions NAME VERSION DB_IMAGE DEPRECATED AGE -2025.10.1 2025.10.1-enterprise docker.io/library/neo4j:2025.10.1-enterprise 12d -2025.11.2 2025.11.2-enterprise docker.io/library/neo4j:2025.11.2-enterprise 12d -2025.12.1 2025.12.1-enterprise docker.io/library/neo4j:2025.12.1-enterprise 12d +2026.05.0 2026.05.0-enterprise docker.io/library/neo4j:2026.05.0-enterprise 14d +2026.06.0 2026.06.0-enterprise docker.io/library/neo4j:2026.06.0-enterprise 14d +2026.07.1 2026.07.1-enterprise docker.io/library/neo4j:2026.07.1-enterprise 14d +2026.08.1 2026.08.1-enterprise docker.io/library/neo4j:2026.08.1-enterprise 14d +5.26.28 5.26.28-enterprise docker.io/library/neo4j:5.26.28-enterprise 14d ``` -Notice the `DEPRECATED` column. A `true` value means that version is deprecated for the current KubeDB release and should be avoided. In this tutorial, we will use `2025.12.1`. +Notice the `DEPRECATED` column. A `true` value means that version is deprecated for the current KubeDB release and should be avoided. In this tutorial, we will use `2026.08.1`. ## Create a Neo4j Database @@ -73,7 +75,7 @@ metadata: namespace: demo spec: replicas: 3 - version: "2025.12.1" + version: "2026.08.1" storage: storageClassName: local-path accessModes: @@ -86,7 +88,7 @@ spec: Here, -- `spec.version` is the name of the `Neo4jVersion` CR specifying the Docker image for each database pod. In this tutorial, Neo4j `2025.12.1` Enterprise is used. +- `spec.version` is the name of the `Neo4jVersion` CR specifying the Docker image for each database pod. In this tutorial, Neo4j `2026.08.1` Enterprise is used. - `spec.replicas` sets the number of Neo4j instances in the cluster. Here, a 3-member cluster is created. - `spec.storage` specifies the `StorageClass` and size of the PVC that KubeDB will dynamically allocate for each pod. This field is required when `spec.storageType` is `Durable` (the default). - `spec.deletionPolicy` controls what KubeDB does when the `Neo4j` CR is deleted. `WipeOut` removes all related resources including PVCs and Secrets. @@ -99,8 +101,8 @@ neo4j.kubedb.com/neo4j-test created $ kubectl get neo4j -n demo neo4j-test -w NAME VERSION STATUS AGE -neo4j-test 2025.12.1 Provisioning 10s -neo4j-test 2025.12.1 Ready 2m +neo4j-test 2026.08.1 Provisioning 10s +neo4j-test 2026.08.1 Ready 2m ``` > If the status stays `Provisioning` for more than a few minutes, run `kubectl describe neo4j -n demo neo4j-test` and check the `Events` section for errors. Common causes are insufficient cluster resources or a missing StorageClass. @@ -114,7 +116,7 @@ Once `status.phase` is `Ready`, all three pods are running and the cluster has f ```bash $ kubectl get neo4j -n demo NAME VERSION STATUS AGE -neo4j-test 2025.12.1 Ready 3m +neo4j-test 2026.08.1 Ready 3m $ kubectl get pods -n demo -l app.kubernetes.io/instance=neo4j-test NAME READY STATUS RESTARTS AGE diff --git a/docs/guides/neo4j/recommendation/recommendation.md b/docs/guides/neo4j/recommendation/recommendation.md index f3283fe070..c61683a5e7 100644 --- a/docs/guides/neo4j/recommendation/recommendation.md +++ b/docs/guides/neo4j/recommendation/recommendation.md @@ -64,7 +64,7 @@ metadata: name: neo4j-recommendation namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" authSecret: kind: Secret name: neo4j-auth @@ -98,7 +98,7 @@ metadata: name: neo4j-recommendation namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" tls: issuerRef: apiGroup: cert-manager.io @@ -138,7 +138,7 @@ metadata: name: neo4j-recommendation namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" ``` In this configuration: @@ -155,7 +155,7 @@ KubeDB monitors the configured lifecycle and generates a VersionUpdate Recommend * If changes are introduced in the existing version image (e.g., security fixes or image updates without a version bump), a recommendation is generated -For example: Recommending version update from `2025.12.1` to `2025.12.2` +For example: Recommending version update from `2026.07.1` to `2026.08.1` Once approved, KubeDB creates an opsrequest to perform the version upgrade automatically, ensuring: @@ -174,7 +174,7 @@ metadata: name: neo4j-recommendation namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" ``` In this configuration: diff --git a/docs/guides/neo4j/reconfigure/reconfigure.md b/docs/guides/neo4j/reconfigure/reconfigure.md index 54ea0b2330..e4ede16a59 100644 --- a/docs/guides/neo4j/reconfigure/reconfigure.md +++ b/docs/guides/neo4j/reconfigure/reconfigure.md @@ -45,7 +45,7 @@ metadata: name: neo4j-test namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: @@ -66,7 +66,7 @@ metadata: name: neo4j-test namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: diff --git a/docs/guides/neo4j/restart/restart.md b/docs/guides/neo4j/restart/restart.md index 1ba7932603..158db828c4 100644 --- a/docs/guides/neo4j/restart/restart.md +++ b/docs/guides/neo4j/restart/restart.md @@ -37,7 +37,7 @@ metadata: name: neo4j-test namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storage: resources: @@ -61,7 +61,7 @@ Wait until `STATUS` shows `Ready` before proceeding. ``` NAME VERSION STATUS AGE -neo4j-test 2025.12.1 Ready 3m +neo4j-test 2026.08.1 Ready 3m ``` ## Apply Restart OpsRequest diff --git a/docs/guides/neo4j/rotate-auth/rotateauth.md b/docs/guides/neo4j/rotate-auth/rotateauth.md index b10255167a..1a035a2963 100644 --- a/docs/guides/neo4j/rotate-auth/rotateauth.md +++ b/docs/guides/neo4j/rotate-auth/rotateauth.md @@ -57,7 +57,7 @@ metadata: name: neo4j-test namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storage: resources: @@ -81,7 +81,7 @@ Wait until `STATUS` shows `Ready` before proceeding. ``` NAME VERSION STATUS AGE -neo4j-test 2025.12.1 Ready 3m +neo4j-test 2026.08.1 Ready 3m ``` --- diff --git a/docs/guides/neo4j/scaling/vertical-scaling/scale-vertically/index.md b/docs/guides/neo4j/scaling/vertical-scaling/scale-vertically/index.md index fcbca07c8d..ce1886544c 100644 --- a/docs/guides/neo4j/scaling/vertical-scaling/scale-vertically/index.md +++ b/docs/guides/neo4j/scaling/vertical-scaling/scale-vertically/index.md @@ -64,7 +64,7 @@ metadata: name: neo4j-test namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storage: resources: @@ -99,7 +99,7 @@ Wait until `STATUS` shows `Ready` before proceeding. ```bash NAME VERSION STATUS AGE -neo4j-test 2025.12.1 Ready 3m +neo4j-test 2026.08.1 Ready 3m ``` --- diff --git a/docs/guides/neo4j/tls/configure/index.md b/docs/guides/neo4j/tls/configure/index.md index 4ffc104ca0..8cc8feaf2f 100644 --- a/docs/guides/neo4j/tls/configure/index.md +++ b/docs/guides/neo4j/tls/configure/index.md @@ -61,7 +61,7 @@ metadata: name: tls-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: @@ -99,7 +99,7 @@ metadata: name: tls-neo4j namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storageType: Durable storage: diff --git a/docs/guides/neo4j/update-version/versionupgrading/index.md b/docs/guides/neo4j/update-version/versionupgrading/index.md index a67de0dc92..876ee51887 100644 --- a/docs/guides/neo4j/update-version/versionupgrading/index.md +++ b/docs/guides/neo4j/update-version/versionupgrading/index.md @@ -65,7 +65,7 @@ metadata: name: neo4j-test namespace: demo spec: - version: "2025.10.1" + version: "2026.07.1" replicas: 3 storage: resources: @@ -89,7 +89,7 @@ Wait until `STATUS` shows `Ready` before proceeding. ``` NAME VERSION STATUS AGE -neo4j-test 2025.10.1 Ready 3m +neo4j-test 2026.07.1 Ready 3m ``` To see all available upgrade targets before proceeding: @@ -97,9 +97,11 @@ To see all available upgrade targets before proceeding: ```bash kubectl get neo4jversions NAME VERSION DB_IMAGE DEPRECATED AGE -2025.10.1 2025.10.1-enterprise docker.io/library/neo4j:2025.10.1-enterprise 2d23h -2025.11.2 2025.11.2-enterprise docker.io/library/neo4j:2025.11.2-enterprise 2d23h -2025.12.1 2025.12.1-enterprise docker.io/library/neo4j:2025.12.1-enterprise 2d23h +2026.05.0 2026.05.0-enterprise docker.io/library/neo4j:2026.05.0-enterprise 14d +2026.06.0 2026.06.0-enterprise docker.io/library/neo4j:2026.06.0-enterprise 14d +2026.07.1 2026.07.1-enterprise docker.io/library/neo4j:2026.07.1-enterprise 14d +2026.08.1 2026.08.1-enterprise docker.io/library/neo4j:2026.08.1-enterprise 14d +5.26.28 5.26.28-enterprise docker.io/library/neo4j:5.26.28-enterprise 14d ``` --- @@ -119,7 +121,7 @@ spec: databaseRef: name: neo4j-test updateVersion: - targetVersion: "2025.12.1" + targetVersion: "2026.08.1" ``` Apply it and wait for completion: @@ -171,10 +173,10 @@ NAME TYPE STATUS AGE neo4j-update-version UpdateVersion Successful 2m57s NAME VERSION STATUS AGE -neo4j-test 2025.12.1 Ready 21m +neo4j-test 2026.08.1 Ready 21m ``` -> ✅ The `VERSION` column now shows `2025.12.1` and `STATUS` is `Ready` — the upgrade is complete. +> ✅ The `VERSION` column now shows `2026.08.1` and `STATUS` is `Ready` — the upgrade is complete. --- @@ -210,9 +212,11 @@ The version must exist as a `Neo4jVersion` catalog entry in your cluster. If the ```bash NAME VERSION DB_IMAGE DEPRECATED AGE -2025.10.1 2025.10.1-enterprise docker.io/library/neo4j:2025.10.1-enterprise 2d23h -2025.11.2 2025.11.2-enterprise docker.io/library/neo4j:2025.11.2-enterprise 2d23h -2025.12.1 2025.12.1-enterprise docker.io/library/neo4j:2025.12.1-enterprise 2d23h +2026.05.0 2026.05.0-enterprise docker.io/library/neo4j:2026.05.0-enterprise 14d +2026.06.0 2026.06.0-enterprise docker.io/library/neo4j:2026.06.0-enterprise 14d +2026.07.1 2026.07.1-enterprise docker.io/library/neo4j:2026.07.1-enterprise 14d +2026.08.1 2026.08.1-enterprise docker.io/library/neo4j:2026.08.1-enterprise 14d +5.26.28 5.26.28-enterprise docker.io/library/neo4j:5.26.28-enterprise 14d ``` Update your KubeDB operator to get the latest catalog. diff --git a/docs/guides/neo4j/volume-expansion/volume-expansion.md b/docs/guides/neo4j/volume-expansion/volume-expansion.md index f90481de34..2b3c51b4da 100644 --- a/docs/guides/neo4j/volume-expansion/volume-expansion.md +++ b/docs/guides/neo4j/volume-expansion/volume-expansion.md @@ -78,7 +78,7 @@ metadata: name: neo4j-test namespace: demo spec: - version: "2025.12.1" + version: "2026.08.1" replicas: 3 storage: resources: @@ -102,7 +102,7 @@ Wait until `STATUS` shows `Ready` before proceeding. ``` NAME VERSION STATUS AGE -neo4j-test 2025.12.1 Ready 3m +neo4j-test 2026.08.1 Ready 3m ``` ---