Install Neo4j cluster cores

Getting everything to work in Kubernetes requires that certain K8s objects have specific names that are referenced elsewhere. Each Neo4j instance is a Helm “release” and has a release name. Release name must consist of lower case alphanumeric characters, - or ., and must start and end with an alphanumeric character.

The following example installations use core-1, core-2, core-3 as release names for the core members.

  1. Install each core member individually using the deployment core-<num>.values.yaml file created in Create Helm deployment values files and the neo4j/neo4j-cluster-core Helm Chart.

    1. Install core-1.

      helm install core-1 neo4j/neo4j-cluster-core -f core-1.values.yaml
      Example output
      NAME: core-1
      LAST DEPLOYED: Fri Nov  5 14:32:10 2021
      NAMESPACE: default
      STATUS: deployed
      REVISION: 1
      TEST SUITE: None
      NOTES:
      Thank you for installing neo4j-cluster-core.
      
      Your release "core-1" has been installed .
      
      The neo4j user's password has been set to "my-password".
      
      This release creates a single Neo4j Core instance. It  will not become ready until it is able to form a working Neo4j cluster by joining other Neo4j Core instances. To create a working cluster requires at least 3 Core instances.
      
      Once you have a working Neo4j cluster you must install at least one Neo4j Service before you can connect applications to Neo4j. Available Neo4j services are:
        neo4j-headless-service - for connecting applications running inside Kubernetes to Neo4j
        neo4j-loadbalancer - for connecting applications running outside Kubernetes to Neo4j
      
      Graphs are everywhere!
    2. Install core-2.

      helm install core-2 neo4j/neo4j-cluster-core -f core-2.values.yaml
      Example output
      NAME: core-2
      LAST DEPLOYED: Fri Nov  5 14:36:14 2021
      NAMESPACE: default
      STATUS: deployed
      REVISION: 1
      TEST SUITE: None
      NOTES:
      Thank you for installing neo4j-cluster-core.
      
      Your release "core-2" has been installed .
      
      The neo4j user's password has been set to "my-password".
      
      This release creates a single Neo4j Core instance. It  will not become ready until it is able to form a working Neo4j cluster by joining other Neo4j Core instances. To create a working cluster requires at least 3 Core instances.
      
      Once you have a working Neo4j cluster you must install at least one Neo4j Service before you can connect applications to Neo4j. Available Neo4j services are:
        neo4j-headless-service - for connecting applications running inside Kubernetes to Neo4j
        neo4j-loadbalancer - for connecting applications running outside Kubernetes to Neo4j
      
      Graphs are everywhere!
    3. Install core-3.

      helm install core-3 neo4j/neo4j-cluster-core -f core-3.values.yaml
      Example output
      NAME: core-3
      LAST DEPLOYED: Fri Nov  5 14:36:32 2021
      NAMESPACE: default
      STATUS: deployed
      REVISION: 1
      TEST SUITE: None
      NOTES:
      Thank you for installing neo4j-cluster-core.
      
      Your release "core-3" has been installed .
      
      The neo4j user's password has been set to "my-password".
      
      This release creates a single Neo4j Core instance. It  will not become ready until it is able to form a working Neo4j cluster by joining other Neo4j Core instances. To create a working cluster requires at least 3 Core instances.
      
      Once you have a working Neo4j cluster you must install at least one Neo4j Service before you can connect applications to Neo4j. Available Neo4j services are:
        neo4j-headless-service - for connecting applications running inside Kubernetes to Neo4j
        neo4j-loadbalancer - for connecting applications running outside Kubernetes to Neo4j
      
      Graphs are everywhere!

      If you have not passed a password for the neo4j user, the Neo4j Helm Chart has automatically generated one for you. The password is the same for all cluster members.

      You can find it in the Helm install outputs. Make a note of it.

  2. Verify that the core members have formed a cluster. See the next section Verify the Neo4j cluster formation.