From f205c9bfabd23fec86bc3673b57ba1ff2c6c2936 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lucas=20Serv=C3=A9n=20Mar=C3=ADn?= Date: Sat, 14 Nov 2020 12:58:40 +0100 Subject: [PATCH] README.md: remove CoreOS-specific install step MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This commit removes a code snippet that is specific to CoreOS Container Linux. Including this in the installation instructions for WireGuard can give the impression that this code works for any cluster. Fixes: #89. Signed-off-by: Lucas Servén Marín --- README.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 57825c7..c3c73ae 100644 --- a/README.md +++ b/README.md @@ -30,13 +30,10 @@ Kilo can be installed on any Kubernetes cluster either pre- or post-bring-up. ### Step 1: install WireGuard -Kilo requires the WireGuard kernel module on all nodes in the cluster. -For most Linux distributions, this can be installed using the system package manager. -For Container Linux, WireGuard can be easily installed using a DaemonSet: - -```shell -kubectl apply -f https://raw.githubusercontent.com/squat/modulus/master/wireguard/daemonset.yaml -``` +Kilo requires the WireGuard kernel module to be loaded on all nodes in the cluster. +Starting at Linux 5.6, the kernel includes WireGuard in-tree; Linux distributions with older kernels will need to install WireGuard. +For most Linux distributions, this can be done using the system package manager. +[See the WireGuard website for up-to-date instructions for installing WireGuard](https://www.wireguard.com/install/). ### Step 2: open WireGuard port