I am attempting to integrate Neo4j with Istio, but I am running into consistent failures with the poststarthook as well as the readiness, liveness, and startup probes. Does anyone have insights into how to get these two components to work together? I am deploying Neo4j using the helm chart.
@vokbreiden95 Hi, unfortunately Istio is not yet supported via Helm charts, we dont test it but AFAIK is something that can be achieved. We would need a lot more insights about how your infrastructure is set up and how you are trying to implement it in order to suggest a workaround.
@bledi.feshti1 I have managed to get the proxy running on the Neo4j pods. However, I have not gotten the DNS to resolve and show the Neo4j browser page in an internet browsing window. We are running the community edition. Is there a setting in the helm chart that needs to be modified to allow this connection? I am consistently getting a 503. From an infrastructure standpoint, everything is set up correctly to access Neo4j in this manner. This should be very similar to the external load balancer that comes with the helm chart. Instead of this, an istio gateway is used to route the traffic with the DNS extension it looks for to a virtual service, to the actual Neo4j service, and then to the pod. Somewhere along the line, the connection is failing. I can localhost in and see the browser which leads me to believe that there is some setting in the helm chart configs that is blocking this.