...
The minimum requirements for the Kubernetes cluster is a single node (1 virtual machine) with the following specs:
Synergy | Focus | Enterprise (Synergy + Focus) | |
---|---|---|---|
CPU cores (x86_64 processor with speed of 2.2 GHz or more) | 8 | 16 | 20 |
RAM | 32GB | 64GB | 80GB |
Free SDD disk space | 500GB | 600GB | 700GB |
OS | We recommend Ubuntu 20.04 LTS Server (Focal Fossa), but you can also use:
|
⚠️ 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.
| |||
Firewall |
| ||
K3s version support | 1.23, 1.24 |
Installation
Ensure the following items are in place and configured:
...
Costs — K3s is 100% open source and there’s no need to pay for any expensive licenses.
Less setup overhead — a lot of time is saved when setting up a new environment because you don’t need to go through a lengthy process of acquiring extra licenses based on how many CPU cores you have. Also, K3s can be installed using only one command.
It supports many Linux distros — K3s supports popular Linux distributions including open source ones, it can also run both on-premise and in the cloud (AWS, Azure, GCP).
It’s fast and lightweight —K3s is packaged as a single <100MB binary and its lightweight architecture makes it faster than stock Kubernetes for the workloads that it runs.
Easy to update — Thanks to its reduced dependencies.
Batteries included — CRI, CNI, service load balancer, and ingress controller are included.
Smaller attack surface — Thanks to its small size and reduced amount of dependencies.
Certified — K3s is an official CNCF project that delivers a powerful certified Kubernetes distribution.
Flexible — you can run K3s using single-node or multi-node cluster setup.
Proxy settings
Info |
---|
Replace |
Note |
---|
The settings below are only valid for clusters that have Secure mode enabled. |
If your proxy is configured to intercept/inspect HTTPS traffic on the fly, then make sure the following hosts are bypassed (not intercepted):
https://charts.master.k3s.getvisibility.com
https://rancher.$RESELLER_NAMEmaster.k3s.getvisibility.com
https://api.master.k3s.getvisibility.com
...