[k_roy]

I’ve never understood the gatekeeping people wrap around kubernetes.

Even with small 3 node cluster of of raspberry pis, you can run anything you can run in simple docker, and have it survive outages/reboots/etc.

At home, I have a few raspberry pis, orangepi RV (riscv nodes), and my main nodes are large high core and RAM VMs running on Proxmox.

Each one has different capabilities. Some have lots of fast storage attached for longhorn, some have 10Gb/25Gb networking, etc.

And the great part is if I wanted to collapse down to just the SBCs? I would just need to scale down some replicas of high men or high cpu stuff I’m testing.

Of course at job, I just pick the node shape and capabilities I need and don’t think about it.

Yeah, I’m probably the exception for running kubernetes at home, but I would argue if you are running more than a handful of docker containers, you should probably be using kubernetes anyway.

Especially if you care about things being up, or want to be able to seamlessly shuffle stuff around for maintenance. Not to mention my entire infrastructure is repeatable with just a small git repo of fluxcd stuff

[edude03]

I'm not personally trying to gatekeep kubernetes, everyone should do what works for them. However, if I'm putting my professional credibility and/or my sleep schedule on the line, I would not advise anyone to do this.

Even at home, I run stuff that needs to be highly available enough that I wouldn't go this route when there are better options.

[k_roy]

I'd love to hear about your HA solution for things like this.

[edude03]

I should blog about it but it's essentially two things

1) "A lot" of nodes, (1 42U rack is one cluster, with battery backup and redundant switching)

2) Hybrid cloud, a few nodes of this particular cluster run in GCP (kind of cheating :P)

[k_roy]

Okay, well you’ve still not highlighted was is the preferred method here, since even with a 42u rack and a cluster in GCP, you still wouldn’t run kubernetes