dominik/k3s
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update 'README.md'

Browse Source
This commit is contained in:
Dominik Chilla 2022-10-26 18:41:07 +00:00
parent fdc1070c29
commit 0df8b4449c
1 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -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 <a name="user-content-canal"></a>
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 <a name="user-content-clustering"></a>
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.