Nuked and back again – a tale of losing and recovering a bare-metal kubernetes cluster (mostly)

https://blog.keyboardvagabond.com/michael-dileos-software-and-tech-blog/nuked-and-back-again-a-tale-of-losing-and-recovering-a-bare-metal-kubernetes

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.

53 points · 4 comments · view on lemmy.world

4 Comments

Anonymouse@lemmy.world · 5 pts · 240d

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.

moonpiedumplings@programming.dev · 2 pts · 240d (1 reply)

Is your flux config public?

ragingHungryPanda@piefed.keyboardvagabond.com · 3 pts · 240d

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

Sunny@slrpnk.net · 1 pts · 240d

Flashbang warning ⚠️