Preparing for a single-node deployment includes configuring the administrator and target hosts. In the single-node configuration, the Kubernetes cluster and Kaspersky Next XDR Expert components are installed on one target host. After preparing the target host and specifying the configuration file, you will be able to deploy Kaspersky Next XDR Expert on the target host by using KDT.
Preparing the administrator host
You first need to prepare a device that will act as the administrator host from which KDT will launch. This host can be either included in the Kubernetes cluster that is created by KDT during the deployment or not. If the administrator host is not included in the cluster, it will be used only to deploy and manage the Kubernetes cluster and Kaspersky Next XDR Expert. If the administrator host is included in the cluster, it will also act as a target host that is used for operation of Kaspersky Next XDR Expert components. In this case, only one host will be used for deployment and operation of the solution.
To prepare the administrator host:
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.
The cgroup v2 technology is supported for the Linux kernel version 2.6.24 or later.
Preparing the target host
The target host is a physical or virtual machine that is used to deploy Kaspersky Next XDR Expert and included in the Kubernetes cluster. The target host manages the Kubernetes cluster, stores metadata, as well as the Kaspersky Next XDR Expert components work on this 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 and Kaspersky Next XDR Expert components are installed.
If you want to run the Kaspersky Next XDR Expert deployment from the target host, you must prepare this host as the administrator host, as described in the previous procedure, and then perform the preparing for the target host.
To prepare the target host:
Since the DBMS will be installed on the target host, you also need to make sure that the target host meets the requirements for the DBMS.
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 unless the target host will be used as the administrator host. KDT will install all necessary software and dependencies during the deployment.
You must install the DBMS before the Kaspersky Next XDR Expert deployment, because in this case the DBMS and Kaspersky Next XDR Expert components will be installed on the same target host, and the DBMS will not be included in the Kubernetes cluster.
/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. The gateway IP address is an IPv4 address (for example, 10.80.23.182). It is specified in the configuration file (the ingress_ip parameter).
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 <console_host>, <admsrv_host>, <kuma_host>, and <api_host>, and <monitoring_host> are service host names, <smp_domain> is a service domain name. These parameters are parts of the service FQDNs, which you can specify in the configuration file. If you do not specify custom values of service host names, the default values are used: console_host—"console", admsrv_host—"admsrv", kuma_host—"kuma", api_host—"api", monitoring_host—"monitoring".
The listed service FQDNs must be resolved to the IP address of the Kubernetes cluster 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.If you use the target host as the administrator host, you must copy the public key to it, too.
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.