this post was submitted on 12 Aug 2025
65 points (100.0% liked)

Selfhosted

60723 readers
314 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Okay Kubernetes people. I am about to build my first cluster with 4 Raspberry Pi 4B 4gb models powered over POE.

I was going to host just some basic stuff on it (forgejo, a couple Ghost Blogs) and try hosting a Mastodon instance.

The documentation mentioned that I should not use the SD cards for database stuff. So I was going to get some super short thumb drives.

What is everyone else's set up look like with raspberry pis? And how important is matching hardware?

I'm sure I'll learn more from reading the documents but this is my concern right now.

(I was also required to upload a photo so have my Latitude D630)

you are viewing a single comment's thread
view the rest of the comments
[–] curled@lemmy.dbzer0.com 7 points 11 months ago (1 children)

Depending on what you're going to do with the cluster, 4gb of RAM per node feels rather limiting.

Anyways, as far as storage goes I'm using 4 compute blades loaded with 4 8gb RAM versions of the CM4, each with a 500gb Samsung PM9A1 running Talos to save a bit on that precious RAM.

Got Talos up and running with some help from Onedr0p's cluster template which saved me a lot of time on the learning curve.

[–] paulcdb@lemmy.world 2 points 11 months ago (1 children)

Ooh, Onedr0p's cluster template looks great so tried it but getting stuck on RPI_EFI.fd

The notes say: create RPI_EFI.fd like here https://www.sidero.dev/v0.6/guides/rpi4-as-servers/#persisting-changes

But that requires setting up sidero which is discontinued and looks like it needs a working talos cluster to get it working anyway, so is there an easier way to generate RPI_EFI.fd ?

I’m also hitting other issues so going to have to wipe the pi I have for PXE anyway so maybe it’ll play nice after a reset. 🤔

[–] curled@lemmy.dbzer0.com 1 points 11 months ago* (last edited 6 months ago)

I initially generated the talos config with the template script, but using talhelper directly offers a bit more flexibility. The first four nodes in this list are the cm4's

https://github.com/SquaredPotato/home-ops/blob/main/talos%2Ftalconfig.yaml

I also wrote down my setup steps, check here:

https://wiki.abchost.nl/s/cm4-talos-setup