You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: