Horizon Cloud Connector 2.0 and Later - Add a Worker Node to a Horizon Cloud Connector Cluster

To support service-level fault tolerance for Horizon Cloud Connector, create a dual-node cluster by adding a worker node to the cluster containing the primary node. The worker node contains a replica of the Horizon Cloud Connector application services.

To add a worker node to a cluster, you first use vSphere Client to deploy the worker node into your pod's vSphere environment. Then you run commands to join the worker node to the cluster containing the primary node.

For an overview of nodes, clusters, and the fault tolerance and high availability features of Horizon Cloud Connector, see Horizon Cloud Connector Clusters, Node-Level High Availability, and Service-Level Fault Tolerance.

Note: This release supports dual-node clusters, node-level high availability, and service-level fault tolerance only for appliances paired with the following types of pods:

• Horizon pods deployed on premises
• Horizon pods deployed in VMC on AWS with all-in-SDDC architecture

Horizon pods deployed in all other environments support single-node clusters consisting of a primary node only and do not support node-level high availability and service-level fault tolerance.

Prerequisites

Ensure that you have completed the following preliminary tasks:

• Deploy the primary node of the cluster and pair Horizon Cloud Connector with your Horizon pod, as described in Download and Deploy the Horizon Cloud Connector into the Pod's vSphere Environment.
• Verify that you have met the DNS, ports, and protocols requirements for ongoing operations between Horizon Cloud and the Horizon Cloud Connector virtual appliance.

Procedure

1. To deploy the worker node, follow the general procedure for deploying the Horizon Cloud Connector appliance as an OVF template, as described in Download and Deploy the Horizon Cloud Connector into the Pod's vSphere Environment. Ensure that you configure the following options.

   • In the Customize template wizard page, enable the Worker Node option. By default, the Worker Node option is deactivated, resulting in a primary node deployment.
   • Configure an SSH public key for the ccadmin user of the worker node. You must enable SSH access to the worker node in order to run the required commands later in this procedure.

2. After the deployment is complete, use vSphere Client to power on the worker node VM. On the blue console screen, make a note of the node's URL for launching the Horizon Cloud Connector configuration portal.

3. Enable SSH access to the worker node for the ccadmin account. See Enable SSH Access to the Horizon Cloud Connector Using a Command Line Interface.

4. Open an SSH session to the primary node in the cluster and run the primary-cluster-config.sh script with the <WORKER_IP> (the IP address of the worker node that you got earlier).

Note: For Horizon Cloud Connector version 2.4.1 and earlier 2.x versions, the primary-cluster-config.sh file is located in the deployed Horizon Cloud Connector appliance in a sbin directory within the /opt/ directory structure.

Run the script with the <WORKER_IP>.

primary-cluster-config.sh -as <WORKER_IP>

5. At the prompt asking if you want to continue connecting to the worker node, type yes.

6. Allow the command to execute without interruption. At the end of the command output, look for lines similar to the following example, talking about the worker-cluster-config.sh script, where <PRIMARY_IP> is the IP address of the primary node VM.

   Please run the following command on worker node to join the cluster:
   worker-cluster-config.sh -a <PRIMARY_IP> <TOKEN 1> <TOKEN 2>
   

   Make a note of this cluster-join command.

7. Open an SSH session to the worker node and run the cluster-join command displayed in the lines you got in the previous step.

   worker-cluster-config.sh -a <PRIMARY_IP> <TOKEN 1> <TOKEN 2>
   

8. After joining the worker node to the cluster, run the following command on the primary node VM to verify the new cluster membership.

   kubectl get nodes -o wide
   

   In the output returned by the command, verify that both the primary node and worker node appear as registered members of the cluster, identified by their IP addresses.