Versions Compared

Version Old Version 22 New Version 23
Changes made by

Ashima Agarwal

Space Sync for Confluence

Saved on

Key

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

...

Synergy

Focus

Enterprise (Synergy + Focus)

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 disk space
⚠️ K3s will be installed in /var

500GB

600GB

700GB

OS

We recommend Ubuntu 20.04.4 LTS Server (Focal Fossa), but you can also use RHEL 8.6, CentOS 7.9 or Suse Linux 15.3.
⚠️ 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. Costs — K3s is 100% open source and there’s no need to pay for any expensive licenses.

  2. 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.

  3. 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).

  4. 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.

  5. Easy to update — Thanks to its reduced dependencies.

  6. Batteries included — CRI, CNI, service load balancer, and ingress controller are included.

  7. Smaller attack surface — Thanks to its small size and reduced amount of dependencies.

  8. Certified — K3s is an official CNCF project that delivers a powerful certified Kubernetes distribution.

  9. Flexible — you can run K3s using single-node or multi-node cluster setup.

Proxy settings

Info

Replace $RESELLER_NAME with the name of the Rancher management server you’ll be registered to.
You can find it in the registration command you received, e.g: https://rancher.CLUSTERNAME.k3s.getvisibility.com/v3/import/....

Note

The list settings below is are only valid for clusters that have Secure Modemode enabled.

If the customer’s your proxy is configured to decrypt encrypted intercept/inspect HTTPS traffic on the fly, then make sure the following hosts are bypassed (not decryptedintercepted) by the proxy:

  1. https://charts.master.k3s.getvisibility.com

  2. https://rancher.$RESELLER_NAME

.k3s.getvisibility.com (or, in case of direct customers https://rancher.master

  1. .k3s.getvisibility.com

)

  2. https://api.master.k3s.getvisibility.com

The customer’s Your internal proxy should be configured to allow the following public urls to be accessible over port 443 (HTTPS):
Note: replace $RESELLER_NAME with the name of the Rancher server which the customer will be connected to.

Code Block
https://assets.master.k3s.getvisibility.com (Custom K3s installation files)
https://images.master.k3s.getvisibility.com (Private Docker registry)
https://charts.master.k3s.getvisibility.com (Private Helm registry)
https://prod-eu-west-1-starport-layer-bucket.s3.eu-west-1.amazonaws.com (Docker registry AWS CDN)
https://rpm.rancher.io (Rancher RPM repo for configuring SELinux packages on RHEL or CentOS)
https://api.master.k3s.getvisibility.com (Private API server)

Plus one of the below:
- for indirect customers:
https://rancher.$RESELLER_NAME.k3s.getvisibility.com (Rancher/Fleet management server)
- for direct customers:
https://rancher.master.k3s.getvisibility.com (Rancher/Fleet management server)

For more details on how to configure Rancher behind a proxy click here.