From 0df8b4449cc59522993c79e0b46621d29704c348 Mon Sep 17 00:00:00 2001 From: Dominik Chilla Date: Wed, 26 Oct 2022 18:41:07 +0000 Subject: [PATCH] Update 'README.md' --- README.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/README.md b/README.md index 5260491..595bfbe 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,6 @@ * [On premises/IaaS](#install-k3s-on-premises) * [Configure upstream DNS-resolver](#upstream-dns-resolver) * [Change NodePort range](#nodeport-range) - * [Install Canal as NetworkPolicy controller](#canal) * [Clustering](#clustering) * [On Docker with k3d](#install-k3s-on-docker-k3d) * [Namespaces and resource limits](#namespaces-limits) @@ -89,18 +88,6 @@ ExecStart=/usr/local/bin/k3s \ 2. Re-load systemd config: `systemctl daemon-reload` 3. Re-start k3s: `systemctl restart k3s.service` -### Install Canal as NetworkPolicy controller -1. Download the yaml manifest Canal: `wget https://docs.projectcalico.org/manifests/canal.yaml -O canal.yaml` -1. Find and enable (uncomment) the env variable `CALICO_IPV4POOL_CIDR` -1. Set the value of `CALICO_IPV4POOL_CIDR` to `10.42.0.0/16` (or your value of `--cluster-cidr` - k3s defaults to `10.42.0.0/16`) -1. Apply the manifest: `kubectl apply -f canal.yaml` -1. Wait a moment and then check if canal was installed successfully -``` -kubectl -n kube-system get pod | grep canal -canal-drmrl 2/2 Running 0 1m -[...] -``` - ### Clustering 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.