Versions Compared

Version Old Version 27 New Version 28
Changes made by

Space Sync for Confluence

Space Sync for Confluence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The minimum requirements for the Kubernetes cluster is a single node (1 virtual machine) with the following specs:

Enterprise (Synergy + Focus)

SynergyEDC

Focus

DDC / DSPM

EDC + DDC + DSPM

CPU cores (x86_64 processor with speed of 2.2 GHz or more)
⚠️ The CPU must support the instructions SSE4.1 SSE4.2 AVX AVX2 FMA

8

16

20

RAM

32GB

64GB

80GB

Free SDD SSD disk space and available Inodes
⚠️ K3s will be installed in /var/lib/rancher so space should be allocated there. We also need 10-20 GB free space at / and /var.

Minimum disk size: 500GB
Minimum available inodes: 32,768,000 for ext4

Minimum disk size: 600GB
Minimum available inodes: 39,321,600 for ext4

Minimum disk size: 700GB
Minimum available inodes: 45,875,200 for ext4

OS

We recommend Ubuntu 20.04 LTS Server (Focal Fossa), but you can also use:

  • RHEL 8.6, 8.7, 8.8 or 9.2

  • CentOS 7.9

  • Suse Linux 15.3

(lightbulb) Please ensure that the OS installed is the Server Edition, regardless of the flavor or version, and that no Desktop Environment is installed.

⚠️ If you are using CentOS or RHEL please refer to the official K3s documentation and our troubleshooting guide for additional setup.

Root access to the server is required during deployment process and may be required for support tickets / troubleshooting.

  • Please ensure the service user account accessing the server, will be deploying the K3s installer has sudo privilege to access and run the installer from the root.

Firewall

  • The K3s server needs port 443/TCP to be open to allow the clients to access Synergy/Focus dashboard and API.

  • Outbound internet access: In order to download the application artifacts (Docker images and binaries), updates and configuration files, the cluster needs a public internet connection with download speed of 40 Mbps or more and upload speed of 8 Mbps or more. To speed up the initial setup process it is recommended to have a download speed of 100 Mbps or more.

K3s version support

1.23, 1.24, 1.26

Other Requirements

Disable SWAP,
For hardened systems, see: Deploying Product in CIS hardened OS or K3s

Installation

Ensure the following items are in place and configured:

  • Domain Name Service (DNS) with public name resolution enabled

  • Network Time Protocol (NTP)

  • Software Update Service - access to a network-based repository for software update packages.

  • Fixed private IPv4 address

  • Unique static hostname

If using proxy, please run this before using curl:

Code Block
export http_proxy="$PROXY_IP"
export https_proxy="$PROXY_IP"

Before installation, it’s recommended to run automatic checks (as root; PRODUCT_NAME is either “enterprise” or “synergy” or “focus“):

Code Block
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh  | PRODUCT_NAME=enterprise ONLY_PRECHECK=true bash -

As root run the following command to install K3s

Code Block
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh | INSTALL_K3S_VERSION="v1.26.10+k3s1" K3S_KUBECONFIG_MODE="644" sh -s - server --node-name=local-01
Info

Few more arguments that can be used to customize the execution of the k3s script:

SKIP_PRECHECK=true to skip the execution of the precheck script while installing k3s service
SKIP_SYSTEM_CHECKS=true to skip the system hardware checking during precheck
SKIP_NETWORK_CHECKS=true to skip the system network connectivity checking during precheck

Example:
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh | INSTALL_K3S_VERSION="v1.26.10+k3s1" K3S_KUBECONFIG_MODE="644" SKIP_PRECHECK=true sh -s - server --node-name=local-01

Run the kubectl registration command:

...