The administrator host is used to deploy and manage the Kubernetes cluster and Kaspersky Next XDR Expert. Kaspersky Next XDR Expert is deployed on the target host by using KDT. KDT runs on the administrator host and connects to the target host via SSH.
In the single node configuration, one target host manages the Kubernetes cluster, stores metadata, and performs the workload of the Kaspersky Next XDR Expert components. The Kubernetes cluster and Kaspersky Next XDR Expert components are installed on this target host. Only the target host is included in the Kubernetes cluster.
Preparing the administrator host
To prepare the administrator host:
The administrator host will not be included in the Kubernetes cluster that is created by KDT during the deployment.
Make sure that the hardware and software on the administrator host meet the requirements for KDT.
On the administrator host, allocate at least 10 GB of free space in the temporary files directory (/tmp) for KDT. If you do not have enough free space in this directory, run the following command to specify the path to another directory:
export TMPDIR=<new_directory>/tmp
Do not install unofficial distributions of Docker packages from the operating system maintainer repositories.
Preparing the target host
To prepare the target host:
A minimum cluster configuration for the single node deployment includes one target host, which acts as the primary and worker nodes. On this primary-worker node, the Kubernetes cluster, Kaspersky Next XDR Expert components, and the DBMS are installed.
Make sure that the hardware and software on the target host meet the requirements for the single node deployment.
For proper functioning of Kaspersky Next XDR Expert, the Linux kernel version must be 5.15.0.107 or later on the target host with the Ubuntu family operating systems
Do not install Docker on the target host. KDT will install all necessary software and dependencies during the deployment.
/etc/default/ufw file, set DEFAULT_FORWARD_POLICY to ACCEPT.KDT will try to install these packages during the deployment from the package repository. You can also install these packages manually.
The curl and libnfs packages are not installed during the deployment from the package repository by using KDT. You must install these packages manually if they are not already installed. The libnfs package version 12 and later is used.
The Kubernetes cluster gateway is intended for connecting to the Kaspersky Next XDR Expert components installed inside the Kubernetes cluster.
Since the DBMS is installed inside the cluster on the primary-worker node, the gateway IP address is an IP range (for example, 192.168.0.1—192.168.0.2). The gateway IP address is specified in the configuration file.
Make sure that the target host and the Kubernetes cluster gateway are located in the same broadcast domain.
By default, the Kaspersky Next XDR Expert services are available at the following addresses:
Where <smp_domain> is a common part of the service FQDNs that you can specify in the configuration file.
The listed service FQDNs must be resolved to the IP address of the Kubernetes cluster gateway. The first IP address of the gateway IP range is the address of the Kaspersky Next XDR Expert services (excluding the DBMS IP address), and the second IP address of the gateway IP range is the IP address of the DBMS. For example, if the gateway IP range is 192.168.0.1—192.168.0.2, the service FQDNs must be resolved as follows:
These accounts are used for the SSH connection and must be able to elevate privileges (sudo) without entering a password. To do this, add the created user accounts to the /etc/sudoers file.
/home/<user_name>/.ssh directory) by using the ssh-copy-id utility.You can use one intermediate certificate that is issued off the organization's root certificate or leaf certificates for each of the services. The prepared custom certificates will be used instead of self-signed certificates.