Automation Suite
2023.10
false
Step 4: Configuring the load balancer - Automation Suite 2023.10
Banner background image
logo
Automation Suite on Linux Installation Guide
Last updated Feb 13, 2024

Step 4: Configuring the load balancer

Overview

A load balancer is mandatory for the multi-node HA-ready production setup.

Automation Suite supports two types of configuration for the load balancer, as shown in the following sections.

You can configure the load balancer to use session persistence or sticky sessions, but it is not a requirement.

Note: Currently, only Layer 4 (network layer) load balancer is supported.

Server and node pool configuration

This is the recommended configuration for the load balancer.

Configuring the backend pool

You need to create two backend pools that meet the following requirements:

  • Server Pool

    • Consists of all the server nodes.
    • There must not be any agent nodes in the Server Pool.
  • Node Pool

    • Consists of all the server nodes and non-specialized agent nodes. Specialized agent nodes include task-mining, gpu, asrobots.

Enabling ports on the load balancer

Ensure you have the following ports enabled on your firewall for the source of load balancer:

Port

Protocol

Purpose

Traffic forwarding

443

TCP

For HTTPS (accessing Automation Suite).

Traffic on this port must be forwarded to Node Pool.

300701

TCP

For accessing the temporary registry during installation and upgrade using HTTP.

Traffic on this port must be forwarded to the Server Pool.

6443

TCP

For accessing Kube API using HTTPS; required for node joining.

Traffic on this port should be forwarded to Server Pool.

9345

TCP

For accessing Kube API using HTTP; required for node joining.

Traffic on this port should be forwarded to Server Pool.

1 If you do not have an external OCI-complaint registry, you must open port 30070 on the load balancer and the server node on which you plan to install the temporary docker registry.
Note:

We recommend not exposing any ports except for the HTTPS one outside the cluster. Run your nodes behind a firewall / security group.

If you have a firewall set up on the network, make sure that it has these ports open to allow traffic.

Configuring the health probes

Probe

Protocol

Port

Interval

Re-entry threshold

Associate pool

https-probe

TCP

443

15 sec

2

Node Pool

kubeapi-probe

TCP

6443

15 sec

2

Server Pool

k8s-probe

TCP

9345

15 sec

2

Server Pool

Refer to the following illustration for more details on the configuration



Alternative configuration

Important:

This configuration does not have resilience to nodes going down during installation.

If the primary server is down or deleted, cluster configuration needs to be updated.

FQDN of the primary server needs to be remapped to a different machine in the cluster that is available.

Configuring the backend pool

Create one backend Pool, as follows:

  • Create a Node Pool

Enabling ports on the load balancer

Ensure that you have the following ports enabled on your firewall for the source of load balancer:

Port

Protocol

Purpose

Traffic forwarding

443

TCP

For HTTPS (accessing Automation Suite).

Traffic on this port should be forwarded to the Node Pool.

Configuring the health probes

Probe

Protocol

Port

Interval

Re-entry threshold

Associate pool

https-probe

TCP

443

15 sec

2

Node Pool

Refer to the following illustration for more details on the configuration.



Support and Services icon
Get The Help You Need
UiPath Academy icon
Learning RPA - Automation Courses
UiPath Forum icon
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.