Adding a Worker Node - non-TufinOS

Overview

This procedure is for adding a worker node to an existing TOS Aurora cluster running RHEL, or Rocky Linux. If you have not yet installed TOS Aurora, on the primary data node, start with Clean Install of TOS Aurora on a Non-TufinOS Server. For all other installation paths such as upgrade or other platforms, see the menu for the appropriate procedure.

You do not need to install TOS on the worker nodes.

Prerequisites

You cannot use IP Tables. All IP tables rules will be flushed when adding the node.
Your primary data node must also be deployed on the same operating system as the worker node.
You must know the resources you will need - CPU cores, RAM, disk space and the load-model parameter, provided by your account team based on the procedure Calculate resources - clean install.
You will need to allow access to required Ports and Services.
If you intend to use syslog, allocate a syslog VIP on the same subnet as your primary VIP.
The node's network IP must be on the same subnet as the cluster primary VIP.
Give the node a unique hostname in the cluster - use the command below, replacing <mynode> with your preferred name:

[<ADMIN> ~]$ sudo hostnamectl set-hostname <mynode>

sudo hostnamectl set-hostname <mynode>

You need to configure a separate partition for /opt,, and the boot disk needs at least 300 GB of available storage. The /opt partition will contain your data, which will increase over time. Most of your available disk space should be allocated to this partition and the minimum is determined by the load model parameter (small, medium, large) provided by your account team. Minimum sizes for all partitions:

Minimum Partition Sizes

Boot disk

/opt/

(Small)*

/opt/

(Medium)*

/opt/

(Large)*

Central cluster / remote cluster primary data node / HA data nodes

300 GB

80 GB

170 GB

370 GB

Worker node (central and remote clusters)

150 GB

70 GB

*Small, medium and large refer to the load model parameter provided by your account team.

We recommend allocating /opt partition all remaining disk space after you have partitioned the boot disk and etcd.

Operating System Requirements

Host: Physical server / VMware ESXi 6.5, 6.7, 7.0 or 8.0, vSphere
OS distribution:
- Red Hat Enterprise Linux 8.9, or 8.10
- Rocky Linux 8.9, or 8.10
Disk(s) SSD with 7,500 IOPS and 250MB/s throughput, or higher.
Language: en-US
The kernel must be up-to-date
SELinux must be disabled
rsync, wireguard and screen must be installed for transferring data, in-cluster encryption and launching shell sessions respectively
Required modules must get loaded using a configuration file /etc/modules-load.d/tufin.conf containing entries:
```
br_netfilter
wireguard
overlay
ebtables
ebtable_filter
```
br_netfilter wireguard overlay ebtables ebtable_filter
Permanent kernel parameters must be set. For example, using a configuration file /etc/sysctl.d/tufin.conf containing entries:
```
net.bridge.bridge-nf-call-iptables = 1
fs.inotify.max_user_watches = 1048576
fs.inotify.max_user_instances=10000
net.ipv4.ip_forward = 1
```
net.bridge.bridge-nf-call-iptables = 1 fs.inotify.max_user_watches = 1048576 fs.inotify.max_user_instances=10000 net.ipv4.ip_forward = 1
Network configurations for your interface must be set to manual IPv4 with gateway and DNS Servers set to the IPs used by your organization.

The system will use a reverse DNS lookup (PTR record) to resolve the DNS IP addresses with the domain name during the TOS installation. Therefore you have to add these PTR records to the DNS server. If you do not, the TOS installation will fail.
You must have permissions to execute TOS CLI commands located in directory /usr/local/bin/tos and to use sudo if necessary.
To run TOS CLI commands without specifying the full path (/usr/local/bin/tos), your environment path must be modified accordingly.
The server timezone must be set.

Procedure

Before you proceed, read and understand Prerequisites - this may prevent unexpected failures.

Configure the operating system.
Add the node to the cluster.

Check the TOS status..

On the primary data node, check the TOS status.
```
[<ADMIN> ~]$ tos status
```
tos status
In the output, check if the System Status is Ok and all the items listed under Components appear as Ok. If this is not the case, contact Tufin Support.

Example output for a central cluster data node:

[<ADMIN> ~]$ tos status         
[Mar 28 13:42:09]  INFO Checking cluster health status           
TOS Aurora
Tos Version: 24.2 (PRC1.1.0)

System Status: "Ok"
            
Cluster Status:
   Status: "Ok"
   Mode: "Multi Node"

Nodes
  Nodes:
  - ["node1"]
    Type: "Primary"
    Status: "Ok"
    Disk usage:
    - ["/opt"]
      Status: "Ok"
      Usage: 19%
  - ["node3"]
    Type: "Worker Node"
    Status: "Ok"
    Disk usage:
    - ["/opt"]
      Status: "Ok"
      Usage: 4%

registry
  Expiration ETA: 819 days
  Status: "Ok"

Infra
Databases:
- ["cassandra"]
  Status: "Ok"
- ["kafka"]
  Status: "Ok"
- ["mongodb"]
  Status: "Ok"
- ["mongodb_sc"]
  Status: "Ok"
- ["ongDb"]
  Status: "Ok"
- ["postgres"]
  Status: "Ok"
- ["postgres_sc"]
  Status: "Ok"

Application
Application Services Status OK
Running services 50/50

Remote Clusters
Number Of Remote Clusters: 2
  - ["RC"]
     Connectivity Status:: "OK:"
  - ["RC2"]
     Connectivity Status:: "OK"

  Backup Storage:
  Location: "Local
s3:http://minio.default.svc:9000/velerok8s/restic/default "
  Status: "Ok"
  Latest Backup: 2024-03-23 05:00:34 +0000 UTC

Example output for a remote cluster data node:

[<ADMIN> ~]$ tos status         
[Mar 28 13:42:09]  INFO Checking cluster health status           
TOS Aurora
Tos Version: 24.2 (PRC1.0.0)

System Status: "Ok"
            
Cluster Status:
   Status: "Ok"
   Mode: "Single Node"

Nodes
  Nodes:
  - ["node2"]
    Type: "Primary"
    Status: "Ok"
    Disk usage:
    - ["/opt"]
      Status: "Ok"
      Usage: 19%
  
registry
  Expiration ETA: 819 days
  Status: "Ok"

Infra
Databases:
- ["mongodb"]
  Status: "Ok"
- ["postgres"]
  Status: "Ok"

Application
Application Services Status OK
Running services 16/16

  Backup Storage:
  Location: "Local
s3:http://minio.default.svc:9000/velerok8s/restic/default "
  Status: "Ok"
  Latest Backup: 2024-03-23 05:00:34 +0000 UTC

After the node is added, we recommend stopping tos and then starting it to enhance the node's performance. This will require downtime.