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 deployments #824

Open
EvanDietzMorris opened this issue Jan 9, 2024 · 0 comments
Open

Neo4j deployments #824

EvanDietzMorris opened this issue Jan 9, 2024 · 0 comments
Assignees

Comments

@EvanDietzMorris
Copy link
Collaborator

Currently Plater has a bundled neo4j deployment, but it's not set up to expose the neo4j browser with an ingress. Another chart in the repo (robokopkg) has an ingress for the neo4j browser, but that chart has extra stuff that is obsolete (the guides server portion) and is a bit complicated by an nginx server and a LoadBalancer instead of a simple ingress (I'm not sure if that stuff is worth it, maybe it is). It would be great if we could expose the neo4j browser for plater neo4j instances, and/or clean up or replace the robokopkg neo4j deployment so that we have a simple way to deploy neo4j instaces where only the browser and bolt/http protocols are exposed. I don't have strong opinions about whether this should be one chart or two. We could probably use the out of the box neo4j charts from somewhere else for the latter case, but we'd need a good way to keep track of and deploy the specific ingress configurations we use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants