Versions Compared

Version Old Version 20 New Version 21
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

...

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

Run the kubectl registration command:

Note

The command below is just an example, it will not work during deployment. For direct customers, Customer Support Team will provide the registration command, otherwise you should have been provided registration command in the Welcome Email.

Code Block
kubectl apply -f https://....k3s.getvisibility.com/v3/import/dxslsxcf84....yaml

...

Note

The list below is only valid for clusters that have Secure mode enabled.

Note: Secure mode is enabled by default in all clusters installations since Jan 2023

Warning

If the customer’s proxy is configured to decrypt encrypted traffic on the fly then make sure the following hosts are bypassed (not decrypted) by the proxy:

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

...

https://rancher.$RESELLER_NAME.k3s.getvisibility.com

...

(or, in case of direct customers https://

...

rancher.master.k3s.getvisibility.com

...

)

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

The customer’s 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://apirancher.master.k3s.getvisibility.com (PrivateRancher/Fleet APImanagement server)

For more details on how to configure Rancher behind a proxy Configuring Rancher and Fleet Agent to Run Behind HTTP Proxy click here.