geerlingguy/turing-pi-2-cluster — explained in plain English
Analysis updated 2026-08-01 · repo last pushed 2023-01-13
Get a working Kubernetes cluster running on a Turing Pi 2 with four Raspberry Pi compute modules in an afternoon.
Set up a remote off-grid cluster with 4G LTE modem connectivity and reverse SSH tunnel access from anywhere.
Monitor cluster health with Prometheus and Grafana dashboards deployed automatically by the scripts.
Verify your cluster works by deploying a sample Drupal website included in the automation.
| geerlingguy/turing-pi-2-cluster | jlevy/simple-modern-uv | farama-foundation/gymnasium-env-template | |
|---|---|---|---|
| Stars | 179 | 281 | 23 |
| Language | Jinja | Jinja | Jinja |
| Last pushed | 2023-01-13 | — | 2024-10-16 |
| Maintenance | Dormant | — | Stale |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | developer | developer | researcher |
Figures from each repo's GitHub metadata at analysis time.
Requires physical Turing Pi 2 hardware with Raspberry Pi compute modules, network configuration, and the project is deprecated in favor of a newer repository.
This repository, created by Jeff Geerling, is a set of automation scripts for setting up a mini-computer cluster on a Turing Pi 2 board. A Turing Pi 2 lets you plug multiple Raspberry Pi compute modules into a single board, essentially creating a tiny, self-contained data center. The scripts automate all the tedious setup work, from configuring the network to installing software, so you end up with a working cluster that can run applications across multiple computers. Note that this project is deprecated, meaning the author has moved active development to a newer repository. The automation is built with Ansible, a tool that lets you control multiple computers from a single workstation. You provide Ansible with a list of your computers (in this case, four Raspberry Pis named turing-node-1 through turing-node-4) and some basic configuration details. When you run the provided playbooks (which are basically instruction files), Ansible connects to each Pi over your network and configures them automatically. It sets up one Pi as the "control plane" (the leader) and the rest as worker nodes, then installs K3s, a lightweight version of Kubernetes that coordinates the cluster. The setup goes beyond basic cluster installation. It can configure a custom network so the cluster operates on its own isolated subnet, which is useful if you want to run it remotely. In fact, the author includes configurations for connecting a 4G LTE modem for off-grid internet, and even sets up a reverse SSH tunnel so you can remotely access the cluster from anywhere. It also configures storage using ZFS, sets up Prometheus and Grafana for monitoring the cluster's health, and deploys a sample Drupal website so you can verify everything works. This is aimed at hobbyists and makers who want to experiment with clustered computing and Kubernetes on physical hardware without spending thousands on enterprise gear. A concrete example would be someone who bought a Turing Pi 2 to learn how distributed systems work, they could use these scripts to get a functional cluster running in an afternoon rather than manually configuring each Pi. The author also used this setup for YouTube videos, so viewers could follow along and replicate his environment. One notable tradeoff: the README warns that the hardware used was a pre-production prototype, so behavior may differ on production boards. The project is also explicitly deprecated in favor of a newer pi-cluster repository, so anyone using it today should be aware it won't receive updates.
Automation scripts that set up a mini Kubernetes cluster on a Turing Pi 2 board with multiple Raspberry Pi compute modules. Deprecated in favor of a newer repository.
Mainly Jinja. The stack also includes Ansible, K3s, ZFS.
Dormant — no commits in 2+ years (last push 2023-01-13).
No license information is provided in the repository, so default copyright restrictions apply and usage rights are unclear.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.