Make, which will be useful for all the runs to not fiddle with parameters.Terraform ( written in 0.13.4, works with 0.14.8 as well ).Mac ( for the card formatting part ), I may update the script with platform detection later when I have time to install the Linux VM.To reproduce results ( or make it work ), you will need: With those in mind, I managed to sit down and started working on coding this little Frankenstein. Principle #3: Raspberry Pi cluster runs in my home network, within its own VLAN, hence why securing it is not my priority, and all the services together with nodes should be accessible easily, without the need for juggling with credentials. It would be nice to utilise it as permanent, shared storage for all the nodes. Principle #2: There’s an NFS server running on my old Intel NUC, connected to the DROBO storage. Setting up the memory card, the nodes' configuration on the system level and finally - spinning up Kubernetes resources. Principle #1: Setting up the Kubernetes cluster on Raspberry Pi can be divided into three parts. This created a bit opinionated environment, but with plenty of logical separation in code between parts, so it should be a bit easier for you, dear reader, to change any parts of the code or comment out whole files to disable few features here and there. However, its benefits will be long-standing ones, allowing me to not worry about the cluster itself and finally treat it as a stable solution towards which I can migrate my whole home infrastructure.īefore commencing any work, I focused on the basics of the basics and established a few principles I followed during the whole process. Make the whole cluster rebuild and production as easy to reproduce as possible.

I’ve done this a few times already, but after all, one more time, never hurt anyone.Īpproach #2: Wake up early and start coding from scratch the ultimate solution to help me this time is to do it once and use it forever. This method, as I’ve proven to myself quite a few times, is prone to errors and mistakes, mostly typos or skipping one or two steps, then trying to figure out what on earth happened for the next half an hour, to wipe everything out and start from the beginning over and over again.

Both of them were time-consuming.Īpproach #1: Wake up early and rebuild things manually following my own article (sic!) and maybe find some room for improvements. I’ve had two options at that time, and I thought them through on my way to bed. Human vs Machine | Credit: comfreak at pixabay Time and effort thoughts

Adguard raspberry pi