This repository holds the original tutorial for "Kubernetes on Raspbian" / Raspberry Pi by Alex Ellis
This guide is part of a larger blog post: Build your own bare-metal ARM cluster.
Pick between k3s
or kubeadm
.
My current recommendation is to use k3s 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:
- faster, and uses fewer resources - 300MB for a server, 50MB for an "agent"
- 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
- doesn't appear to run into some of the complicated issues we've seen with
kubeadm
Start now:
My current thinking is that only advanced users should attempt to install Kubernetes with kubeadm
. Historically, it's had some unfortunate issues around timeouts and being slow.
- Start the guide: Kubernetes on (vanilla) Raspbian Lite
Once you're up and running please share your clusters on Twitter with @alexellisuk.
You can also join the OpenFaaS Slack community's dedicated channel for ARM and Raspberry Pi #arm-and-pi. Just email alex at openfaas dot com for your invitation.
You're welcome to make use of this guide and to refer to it, but please do not copy it or pass it off as your own without giving attribution to the author(s). If you have suggestions or have found that some of the instructions have fallen out of date, then please see the Contributions section below on how to contribute.
- Jim Angel's Kubernetes cluster for testing unreleased alpha / beta k8s versions
- roncrivera's 4-node home-lab running OpenFaaS in a gun-case
- Scott Hanselman's 6-node cluster running Kubernetes, OpenFaaS with the Pimoroni blinkt! Scott's cluster-selfie
- Ken Fukuyama's Kubernetes cluster running OpenFaaS from Japan
- Karol Stępniewski's Asus Tinkerboard cluster running OpenFaaS and K8s
- Bart Plasmeijer's K8s cluster
- Burton Rheutan's cluster stashed away in a closet
- Kevin Turcios' OpenFaaS cluster
- Estelle Auberix' OpenFaaS and K8s cluster for ServerlessConf Paris
- Davy's Kubernetes and OpenFaaS cluster
- Jaigouk Kim's OpenFaaS and K8s cluster with the Asus Tinkerboard
- Ram's 7-node homelab with OpenFaaS and Kubernetes
- David Muckle's OpenFaaS cluster
- Brian Moelk's battery-powered OpenFaaS cluster
- Marcus Smallman' DIY Raspberry Pi Kubernetes Cluster
- Mathias Deremer-Accettone's Serverless sur Raspberry PI avec Docker Swarm et OpenFaas
- Daniel Llewellyn's three node Raspberry Pi Swarm
- Gareth Bradley's 6 node Raspberry Pi Kubernetes Cluster
- Andreas Muttscheller's Raspberry Pi OpenFaaS k3s cluster provisioned with Ansible
- Ruan Bekker's K3s Setup with Golang and Traefik on a Raspberry Pi 4
Submit your cluster and description by creating a GitHub issue.
- "Kubernetes on Raspbian" with Ansible by Chris Short
- "Kubernetes on Raspbian" for .NET Core / Windows developers by Scott Hanselman
- "Kubernetes on Raspbian" broken-up into bash scripts with a custom laser-cut design by Kasper Nissen
- "Kubernetes on Raspbian" with Packer by Cody Bunch
- "Kubernetes on Raspbian" adapted for HypriotOS by Edouard Lafargue
- Make your very own Kubernetes cluster from Raspberry PI - unattributed, copy/paste from this guide/repository
Contributions are welcome, but must be tested and justified.
Please make sure each commit is signed off with git commit -s
(this means don't edit in the GitHub UI).
See below for more information.
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.