Verify the read replica has joined the cluster
You check the pods and services to verify that the read replica has joined the cluster, which might take a few minutes. In the end, you should have a cluster with three cores and one read replica:
-
Check that the pods are
READY
:kubectl get pods
NAME READY STATUS RESTARTS AGE core-1-0 1/1 Running 0 10m core-2-0 1/1 Running 0 10m core-3-0 1/1 Running 0 10m rr-1-0 1/1 Running 0 5m15s
-
Check that the services look good:
kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE core-1 ClusterIP 10.112.0.8 <none> 7687/TCP,7474/TCP 22h core-1-admin ClusterIP 10.112.6.162 <none> 6362/TCP,7687/TCP,7474/TCP 22h core-1-internals ClusterIP None <none> 6362/TCP,7687/TCP,7474/TCP,7688/TCP,5000/TCP,7000/TCP,6000/TCP 22h core-2 ClusterIP 10.112.8.77 <none> 7687/TCP,7474/TCP 22h core-2-admin ClusterIP 10.112.9.168 <none> 6362/TCP,7687/TCP,7474/TCP 22h core-2-internals ClusterIP None <none> 6362/TCP,7687/TCP,7474/TCP,7688/TCP,5000/TCP,7000/TCP,6000/TCP 22h core-3 ClusterIP 10.112.8.68 <none> 7687/TCP,7474/TCP 22h core-3-admin ClusterIP 10.112.15.3 <none> 6362/TCP,7687/TCP,7474/TCP 22h core-3-internals ClusterIP None <none> 6362/TCP,7687/TCP,7474/TCP,7688/TCP,5000/TCP,7000/TCP,6000/TCP 22h kubernetes ClusterIP 10.112.0.1 <none> 443/TCP 134d rr-1 ClusterIP 10.112.14.65 <none> 7687/TCP,7474/TCP 22h rr-1-admin ClusterIP 10.112.9.86 <none> 6362/TCP,7687/TCP,7474/TCP 22h rr-1-internals ClusterIP None <none> 6362/TCP,7687/TCP,7474/TCP,7688/TCP,6000/TCP 22h
For more information about the Neo4j services, see Access a Neo4j cluster.