Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Neo4j version mismatch in k8s helm charts vs docker requirements #2103

Open
rezasafi opened this issue Feb 17, 2023 · 6 comments
Open

Neo4j version mismatch in k8s helm charts vs docker requirements #2103

rezasafi opened this issue Feb 17, 2023 · 6 comments
Labels
status:needs_triage For all issues that need to be processed

Comments

@rezasafi
Copy link

I can see that the helm chart on amundsen git references an older image(version 3.3.0) of neo4j here. However services like metadata are using a newer version as you can see here.
I tried upgrading the helm chert image tag and made it work to some extent by disabling ssl and by adding/changing the following configs in configmap-neo4j.yaml under helm charts in amundsen like following:

dbms.connector.bolt.tls_level=DISABLED
dbms.ssl.policy.bolt.client_auth=NONE
dbms.ssl.policy.bolt.enabled=false

And also I updated the following curls in values file to use the jar for neo4j 4.4.x:
curl -L https://github.com/neo4j-contrib/neo4j-apoc-procedures/releases/download/4.4.0.12/apoc-4.4.0.12-all.jar -O
and removing the curl for neo4j-graph-algorithms since they have not provide a release for neo4j 4.4.x.

Still after above changes the metadata service had issues talking to neo4j.
Also databuilder newest version requires 4.4.5 or newer driver for neo4j.
It seems that upgrading the neo4j in helm chart is not trivial and the version mismatches makes it a little confusing.

what is the recommendation when using amundsen on k8s? is it possible to use neo4j 4.4.x with amundsen on k8s? or it is recommended to use older version as it is currently being used in helm charts?

@boring-cyborg
Copy link

boring-cyborg bot commented Feb 17, 2023

Thanks for opening your first issue here!

@Golodhros Golodhros added the status:needs_triage For all issues that need to be processed label Mar 13, 2023
@stale
Copy link

stale bot commented Apr 6, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Apr 6, 2023
@stale
Copy link

stale bot commented May 9, 2023

This issue has been automatically closed for inactivity. If you still wish to make these changes, please open a new pull request or reopen this one.

@stale stale bot closed this as completed May 9, 2023
@DSchmidtDev
Copy link

would like to bring this issue up again :)

@Golodhros Golodhros reopened this Jul 7, 2023
@stale stale bot removed the stale label Jul 7, 2023
@Golodhros Golodhros added stale and removed stale labels Jul 7, 2023
@helloimowen
Copy link

Ran into a similar issue as well. Databuilder as of v7.0.0 does not have a compatible Bolt client, so does not work with the current neo4j version in the provided helm setup.

@jdavidheiser
Copy link
Contributor

@allisonsuarez as author of #1952 do you have any guidance on how to install neo4j in Kube to be compatible with your recent changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:needs_triage For all issues that need to be processed
Projects
None yet
Development

No branches or pull requests

5 participants