...
| EDC | DDC / DSPM | EDC + DDC + DSPM |
---|
CPU | 8 cores | 16 cores | 20 cores |
⚠️ The CPU must support the instructions SSE4.1, SSE4.2, AVX, AVX2, FMA. Only x86_64 architecture is supported. Minimum CPU speed is 2.2 GHz |
Memory | 32GB | 64GB | 80GB |
Storage | 500GB Min available inodes for ext4: 32M | 600GB Min available inodes for ext4: 39M | 700GB Min available inodes for ext4: 45M |
Storage details | only SSD storage is supported SWAP must be disabled minimum 20 GB allocated at /var at least 80% allocated at / rootrequires at least 20GB /var requires at least 20GB /var/lib/rancher requires at least 500GB (in case of EDC, use the correct disk space according to the type of deployment shown above).
if neither /var nor /var/lib/rancher is specifically assigned to a partition you must assign the full 500GB to root if /var is specifically assign to a partition but /var/lib/rancher is not, then you must assign the 500GB to /var if /var/lib/rancher is specifically assign to a partition but /var is not, then you must assign the 500GB to /var/lib/rancher
|
Operating System | Ubuntu 20.04 LTS Server is recommended, other supported operating systems include: Only Server edition versions are supported. No Desktop Environment installed. No other linux distributions are supported. Note |
---|
Root access to the server is required necessary during the deployment process and may also be required for support tickets / and troubleshooting. Please ensure that the service user account accessing the server , will be and deploying the K3s installer has sudo privilege privileges to access and run the installer from the as root. |
|
Firewall | Port 443/TCP to be open to allow the clients to access dashboard and API To download the application artifacts (Docker images and binaries), updates, and configuration files, the cluster needs requires a public internet connection with a minimum download speed of 40 Mbps or more and an upload speed of 8 Mbps or more. To speed up the initial setup process it is recommended to have . For a faster initial setup, a download speed of 100 Mbps or more is recommended.
|
K3s version support | 1.23, 1.24, 1.26 |
Other requirements | Domain Name Service (DNS) with public name resolution enabled Network Time Protocol (NTP) service configured Internet access to a network-based repository for software update packages Fixed private IPv4 address Unique static hostname
For hardened systems, see: Deploying Product in CIS hardened OS or K3s When deploying using RHEL / CentOS / Suse: When deploying using Ubuntu: |
Installation
Info |
---|
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“):please use the following command to see if product requirements are met, using (synergy|focus|dspm|enterprise|ultimate) for PRODUCT_NAME.
Code Block |
---|
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh | PRODUCT_NAME=enterprise ONLY_PRECHECK=true bash - |
As root run Run k3s installer using the following command to install K3sas root user:
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 |
...