Hi!
Anyone can do a successful deployment of a Neo4j 4.0 image on Kubernetes?
I have a lot of problems!
Hi Mariano - we're still in the process of upgrading our helm charts internally for 4.0. In particular a key challenge with the change to 4.0 that you may be encountering is the SSL subsystem; previously Neo4j generated its own self-signed certificate. Configuration that enabled https by default used that, and there were some changes in 4.0 that make startup require extra steps to generate that self-signed certificate. You can certainly post your challenges here and I'll follow up later if I can - but for now also be aware that updated helm charts for GKE are already in the works.
Perfect!
I deploy a Neo4j single instance and wait for de GA of the Cluster of 4.0
Hi David, any news on this?
Will the helm chart be the only deployment option or do you have/plan other ways (kustomize, operator)?
Sorry - no update. The status is the same as above right now.
I'm going to left this here...
https://drive.google.com/open?id=1SZeSOI_-Jw897tgWeL3QxUxKW7mkXMZs
Has a few changes to work in AKS.
And... maybe you can adjust the memory and CPU
1 Like
UPDATE: a PR is pending to get 4.0 support for Neo4j into the stable helm chart in the public helm repo.
helm:master
← moxious:master
opened 12:19PM - 13 Apr 20 UTC
#### What this PR does / why we need it:
- Neo4j [released a major new versio… n (4.0)](https://neo4j.com/press-releases/announcing-neo4j-4-0/) which has a bunch of substantial new features: multi-database, fine-grained security, fabric queries, and others. This version has some substantial differences/incompatibilities from the old series (3.5) that the old chart is based on
- Fixes #21439 by enabling custom configuration to be passed to all pods with a simple configmap name.
- Adds simple readiness and liveness probes, for indications of when cluster formation has been successful.
- Adds APOC installed by default. Most users want APOC in, so this has been done by default with a toggle (useAPOC) which can be trivially set to false if APOC is not wanted. This saves users from setting up initContainers themselves each time.
- Adds a service for contacting read replicas. This is useful when read-only analytic workloads need to be pointed to an auto-scaling subset of cluster members.
- Adds a lot of useful Links, References, and additional documentation for people who use the chart with information on techniques like backup & recovery for Neo4j in Kubernetes
So this PR enables a major new set of features with Neo4j 4.0. As such, and because the underlying product versions were revised by a major version, the chart version is going up a major version as well.
#### Special notes for your reviewer:
#### Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
- [x] [DCO](https://github.com/helm/charts/blob/master/CONTRIBUTING.md#sign-your-work) signed
- [x] Chart Version bumped
- [x] Variables are documented in the README.md
- [x] Title of the PR starts with chart name (e.g. `[stable/mychartname]`)
1 Like
UPDATE: PR is merged, Neo4j 4.0 is available as a helm chart now: charts/stable/neo4j at master · helm/charts · GitHub
1 Like