From a0a65ee3eaf4d078b26a10542501d514b9c92483 Mon Sep 17 00:00:00 2001 From: Dominik Chilla Date: Mon, 20 Sep 2021 00:09:07 +0200 Subject: [PATCH] cosmetics --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 81498e6..4b8800d 100644 --- a/README.md +++ b/README.md @@ -110,7 +110,7 @@ ExecStart=/usr/local/bin/k3s \ If you want to build a K3s-cluster the default networking model is *overlay@VXLAN*. In this case make sure that * all of your nodes can reach (ping) each other over the underlying network (local, routed/vpn). This is required for the overlay network to work properly. VXLAN spans a mashed network over all K3s-nodes. * if your nodes are spread over public networks (like the internet) use a VPN (like IPSec or OpenVPN) to secure the traffic between the nodes. **VXLAN uses plain UDP for transport!** -* if your nodes are connected through VPN, `flannel` (overlay network daemon) explicitly communicates over the vpn network interface instead of the public network interface. Following settings should be made on the nodes: +* if your nodes are connected through VPN, `flannel` (overlay network daemon) should explicitly communicate over the vpn network interface instead of the public network interface. Following settings should be made on the nodes: ``` /etc/systemd/system/k3s-agent.service: