I've installed neo4j after playing with it in Sandbox onto my Kubernetes cluster using the official stable/neo4j helm chart.
I would like to make this neo4j cluster accessible remotely (not just within the Kubernetes cluster) so I've written a service to expose the bolt port. The cluster has one LEADER & two FOLLOWER role servers, which is great for redundancy. However, when I try and access my service, it's a gamble as to whether I'll be served a LEADER or a FOLLOWER.
If I'm connected to a follower and I attempt a write, I get -
Neo.ClientError.Cluster.NotALeader: No write operations are allowed directly on this database. Writes must pass through the leader. The role of this server is: FOLLOWER
Here is my service -
apiVersion: v1 kind: Service metadata: name: pool1-neo4j-nodeport namespace: neo4j spec: type: NodePort ports: - port: 7687 nodePort: 30725 protocol: TCP selector: app: neo4j component: core release: pool1
Am I missing something, is there something specific I need to do? I've also raised an issue on the Helm package.