...
Prerequisites
Please refer to https://getvisibility.atlassian.net/wiki/spaces/KBTESGS/pages/10816717488801305/K3s+Installation#Requirements for the node specs of the product you’ll be installing.
...
K3s needs the following ports to be accessible by all other nodes running in the same cluster:
Protocol | Port | Description |
|---|---|---|
TCP | 6443 | Kubernetes API Server |
⚠️ UDP | 8472 | Required for Flannel VXLAN |
TCP | 2379-2380 | embedded etcd |
TCP | 10250 | metrics-server for HPA |
TCP | 9796 | Prometheus node exporter |
| Note |
|---|
The ports above should not be publicly exposed as they will open up your cluster to be accessed by anyone. Make sure to always run your nodes behind a firewall/security group/private network that disables external access to the ports mentioned above. |
...
The following port must be publicly exposed in order to allow users to access Synergy or Focus product:
Protocol | Port | Description |
|---|---|---|
TCP | 443 | Focus/Synergy backend |
The user must not access the K3s nodes directly, instead, there should be a load balancer sitting between the end user and all the K3s nodes (master and worker nodes):
...
Timeout: 10 seconds
Healthy threshold: 3 consecutive health check successes
Unhealthy threshold: 3 consecutive health check failures
Interval: 30 seconds
Balance mode: round robin
Public
Please refer to https://getvisibility.atlassian.net/wiki/spaces/KBTESGS/pages/10816717488801305/K3s+Installation#Proxy-settings for the list of urls you need to enable in your corporate proxy in order to connect to our private registries.
...
| Code Block |
|---|
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh | INSTALL_K3S_VERSION="v1.2326.910+k3s1" K3S_KUBECONFIG_MODE="644" sh -s - server --node-name=master1 --cluster-init |
...
| Code Block |
|---|
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh | K3S_TOKEN=SHARED_SECRET INSTALL_K3S_VERSION="v1.2326.910+k3s1" K3S_KUBECONFIG_MODE="644" sh -s - server --node-name=master2 --server https://<ip or hostname of master1>:6443 |
...
| Code Block |
|---|
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh | K3S_TOKEN=SHARED_SECRET INSTALL_K3S_VERSION="v1.2326.910+k3s1" K3S_KUBECONFIG_MODE="644" sh -s - server --node-name=master3 --server https://<ip or hostname of master1>:6443 |
...
| Code Block |
|---|
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh | K3S_TOKEN=SHARED_SECRET INSTALL_K3S_VERSION="v1.2326.910+k3s1" K3S_KUBECONFIG_MODE="644" sh -s - agent --node-name=worker1 --server https://<ip or hostname of any master node>:6443 |
Joining additional worker nodes
You may create as many additional worker nodes as you want.
...
| Code Block |
|---|
curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh | K3S_TOKEN=SHARED_SECRET INSTALL_K3S_VERSION="v1.2326.910+k3s1" K3S_KUBECONFIG_MODE="644" sh -s - agent --node-name=workerX --server https://<ip or hostname of any master node>:6443 |
...
| Code Block |
|---|
kubectl get nodes |
Register HA K3s Cluster to Rancher
You may run the registration command that you generated using Rancher UI or through license manager. You should see all master and worker nodes in your cluster through the Machine Pools on the Rancher dashboard:
...