Kaspersky Next XDR Expert

Pre-check of infrastructure readiness for deployment

After you start the deployment of Kaspersky Next XDR Expert, KDT checks whether the hardware, software, and network configuration of the Kubernetes cluster nodes meet the prerequisites for installing the solution. A pre-check is performed for each node of the cluster.

All checks are divided into two groups:

• Strict checks

  Checking the parameters that are critical for the operation of Kaspersky Next XDR Expert. If this check fails, the deployment is interrupted.

• Non-strict checks

  Checking the parameters that are not critical for the operation of Kaspersky Next XDR Expert. If this check fails, the deployment continues.

The following pre-checks are performed:

• Hardware:
  • Free space on disks is enough for deployment.
  • CPU configuration meets the requirements.
  • Free RAM space is enough for deployment.
  • CPU supports the AVX, SSE2, and BMI instructions.
• Software:
  • Operating system and its version meet the requirements.
  • Kernel version meets the requirements.
  • Systemctl is installed and available (strict check).
  • Update of the package manager cache is available (strict check).
  • Required packages of the correct version are installed on the node (strict check).
  • Prohibited packages (docker and podman) are not installed on the node (strict check).
  • Outdated k0s binaries are missing (strict check).
  • Outdated k0s configuration files are missing (strict check).
• Network:
  • All cluster nodes are located in the same broadcast domain.
  • DNS name resolution on the node is available (strict check).
  • Time synchronization on cluster nodes is configured (strict check).
  • Required ports are available.

If all the strict pre-checks are successfully completed, KDT deploys the Kaspersky Next XDR Expert components within the Kubernetes cluster on the target hosts. The results of all passed and failed checks are saved on each node in the file /tmp/k0s_report.txt. You can skip the pre-checks before the deployment, if needed (set the ignore_precheck installation parameter to true).