High Availability using External Load Balancer

You may use any external load balancer for high availability of your Kubernetes cluster. This document covers the configuration of an NGINX as an external load balancer for an RKE2 Kubernetes cluster.

Deployment Prerequisites

Load Balancer Hardware Requirements

Load Balancer without HA is the single point of failure in the cluster setup and customers are required to set up either of the above in a failover cluster.

Configuration Steps

1. DNS configurations

In your DNS, map your FQDN to a record or a CNAME pointing to the load balancer IP or hostname. Given below is a sample configuration for NGINX as an ELB.

2. Deploy an ELB

3. Deploy the cluster in HA using LoadBalancer

3.1. Deploy RKE2 on the first control plane

1. Create a deployment manifest called config.yaml for the RKE2 cluster and replace the IP address.

Assuming that the Load balancer is running on 1.1.1.1 with the FQDN cx.customer-x.com.

cat<<EOF|tee /etc/rancher/rke2/config.yaml
tls-san:
  - cx.customer-x.com
  - 1.1.1.1
write-kubeconfig-mode: "0600"
etcd-expose-metrics: true
cni:
  - canal

EOF

2. For the first control plane setup, install RKE2 RKE2 Control plane Deployment

3. Retrieve the joining token from the control plane you need to use to install the remaining control plane nodes.

   BASH

   cat /var/lib/rancher/rke2/server/node-token

3.2. Deploy RKE2 on remaining control plane nodes

1. Create a deployment manifest called config.yaml 

Assuming that the Load balancer is running on 1.1.1.1 with the FQDN cx.customer-x.com.

cat<<EOF|tee /etc/rancher/rke2/config.yaml
server: https://1.1.1.1:9345
# speicfy the token as retrieved in the first control plane deployment
token: [token-string]
tls-san:
  - cx.customer-x.com
write-kubeconfig-mode: "0644"
etcd-expose-metrics: true
cni:
  - canal

EOF

2. Install RKE2 RKE2 Control plane Deployment on all the remaining control plane nodes.

4. Deploy Worker Nodes

Follow the Deployment Prerequisites from RKE2 Control plane Deployment for each worker node before deployment i.e disable firewall on all worker nodes.

On each worker node, make sure a unique hostname is set beforehand.

To set a hostname, run the following command:-

hostnamectl set-hostname <hostname>

To check the hostname, run the following command:-

hostname

Once hostnames are set, follow these commands on each node to deploy worker nodes.

1. Run the following command to install the RKE2 agent on the worker.

   CODE

   curl -sfL https://get.rke2.io | INSTALL_RKE2_TYPE="agent" sh -

2. Enable the rke2-agent service by using the following command.

   CODE

   systemctl enable rke2-agent.service

3. Create a directory by running the following commands.

   CODE

   mkdir -p /etc/rancher/rke2/

4. Add/edit /etc/rancher/rke2/config.yaml and update the following fields.

   1. <Control-Plane-IP> This is the IP for the first control-plane node.

   2. <Control-Plane-TOKEN> This is the token from Step 2.

      CODE

      server: https://<Control-Plane-IP>:9345
      token: <Control-Plane-TOKEN>

5. Start the service by using the following command.

   CODE

   systemctl start rke2-agent.service

At this point, you have the RKE2 Kubernetes cluster ready using a load balancer.

5. Verify the cluster setup

On the control-plane node run the following command to verify that the worker(s) have been added.

kubectl get nodes -o wide

Next Steps

1. Choose and install a cloud-native storage. See Storage Solution - Getting Started for choosing the right storage solution for your deployment.

2. Deploy Expertflow CX following Expertflow CX Deployment on Kubernetes