Nuked and back again – a tale of losing and recovering a bare-metal kubernetes cluster (mostly) (blog.keyboardvagabond.com)
from ragingHungryPanda@piefed.keyboardvagabond.com to selfhosted@lemmy.world on 06 Dec 02:26
https://piefed.keyboardvagabond.com/c/selfhosted/p/165931/nuked-and-back-again-a-tale-of-losing-and-recovering-a-bare-metal-kuberne

It started with a perfectly good and running kubernetes cluster hosting fediverse applications at keyboardvagabond with all the infrastructure and observability that comes with it. Then I made a simple networking fix.

#disasterrecovery #kubernetes #selfhosted #selfhosting #talos

threaded - newest

Anonymouse@lemmy.world on 06 Dec 13:28 next collapse

A pretty good read. I’ve made many of these mistakes myself and learned from every one of them. We spend so much time hardening our home labs from the bad guys, I wonder if we should instead focus on hardening from ourselves.

Of course, the answer is both.

Sunny@slrpnk.net on 06 Dec 14:43 next collapse

Flashbang warning ⚠️

moonpiedumplings@programming.dev on 06 Dec 20:30 collapse

Is your flux config public?

ragingHungryPanda@piefed.keyboardvagabond.com on 07 Dec 01:13 collapse

it isn’t, I’m hosting a private gitea instance on a home computer.