sascha/k8s-on-raspbian
1
0
Fork 0
mirror of https://github.com/teamserverless/k8s-on-raspbian.git synced 2025-01-18 12:05:31 +00:00
Code Issues Releases Wiki Activity

Update k3d blog posts

Browse Source 
Adds note from #22 - although no specifics have been given on the
issue, this means #22 can be closed.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
This commit is contained in:
Alex Ellis (OpenFaaS Ltd) 2019-12-01 19:42:49 +00:00
parent 449ef5b89c
commit cb74c04c4f
2 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
GUIDE.md
View File

@ -95,6 +95,12 @@ $ sudo dphys-swapfile swapoff && \
sudo update-rc.d dphys-swapfile remove sudo update-rc.d dphys-swapfile remove
``` ```
For Debian, also run:
```sh
sudo systemctl disable dphys-swapfile
```
This should now show no entries: This should now show no entries:
``` ```

10
README.md
View File

@ -12,16 +12,20 @@ Pick between `k3s` or `kubeadm`.
#### 1) Pick `k3s` (recommended) #### 1) Pick `k3s` (recommended)
My current recommendation is to use [k3s](https://k3s.io) from Rancher Labs. It is normal Kubernetes and passes the conformance tests written by the CNCF. I'm yet to be convinced of why someone wouldn't use this for a hobbyist build and I've been pleasantly surprised by it. My current recommendation is to use [k3s](https://k3s.io) from Rancher Labs. It is normal Kubernetes and passes the conformance tests written by the CNCF. I'm yet to be convinced of why someone wouldn't use this for a hobbyist build and I've been pleasantly surprised by it. Rancher Labs offers commercial support and k3s is GA, even more reason to use this option.
k3s is: k3s is:
* faster, and uses fewer resources * faster, and uses fewer resources - 300MB for a server, 50MB for an "agent"
* well-maintained and ARMHF / ARM64 just works * well-maintained and ARMHF / ARM64 just works
* HA is available as of k3s 1.0 along with Kubernetes 1.16
* still normal, upstream, compliant Kubernetes * still normal, upstream, compliant Kubernetes
* doesn't appear to run into some of the complicated issues we've seen with `kubeadm` * doesn't appear to run into some of the complicated issues we've seen with `kubeadm`
Start now: [Will it cluster? k3s on your Raspberry Pi](https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/) Start now:
* [Kubernetes Homelab with Raspberry Pi and k3sup](https://blog.alexellis.io/raspberry-pi-homelab-with-k3sup/)
* [Will it cluster? k3s on your Raspberry Pi](https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/)
#### 2) Or pick `kubeadm` (advanced users) #### 2) Or pick `kubeadm` (advanced users)