Added wireguard port on networking installation

This commit is contained in:
Roberto Bonafiglia
2022-04-08 10:31:33 +02:00
committed by GitHub
parent 1d75de87df
commit 62f23aaa34
@@ -44,7 +44,7 @@ K3s performance depends on the performance of the database. To ensure optimal sp
The K3s server needs port 6443 to be accessible by all nodes.
The nodes need to be able to reach other nodes over UDP port 8472 when Flannel VXLAN is used. The node should not listen on any other port. K3s uses reverse tunneling such that the nodes make outbound connections to the server and all kubelet traffic runs through that tunnel. However, if you do not use Flannel and provide your own custom CNI, then port 8472 is not needed by K3s.
The nodes need to be able to reach other nodes over UDP port 8472 when Flannel VXLAN is used or UDP ports 51820 and 51821 (when using IPv6) when Flannel Wireguard backend is used. The node should not listen on any other port. K3s uses reverse tunneling such that the nodes make outbound connections to the server and all kubelet traffic runs through that tunnel. However, if you do not use Flannel and provide your own custom CNI, then the ports needed by Flannel are not needed by K3s.
If you wish to utilize the metrics server, you will need to open port 10250 on each node.
@@ -59,6 +59,8 @@ If you plan on achieving high availability with embedded etcd, server nodes must
|-----|-----|----------------|---|
| TCP | 6443 | K3s agent nodes | Kubernetes API Server
| UDP | 8472 | K3s server and agent nodes | Required only for Flannel VXLAN
| UDP | 51820 | K3s server and agent nodes | Required only for Flannel Wireguard backend
| UDP | 51821 | K3s server and agent nodes | Required only for Flannel Wireguard backend with IPv6
| TCP | 10250 | K3s server and agent nodes | Kubelet metrics
| TCP | 2379-2380 | K3s server nodes | Required only for HA with embedded etcd