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.
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.
the instances were an excuse for me to set up a cluster. I definitely know none of this isn’t needed. I wanted to get familiar with things that I do related to work, but never really get to get my hands dirty with. I did all of this because I wanted to learn.
I suggest framing the blog post this way. The way it reads now is like you’re actually suggesting this to other small instance admins. I think it’s OK to play around with new tools, but the article is not self aware in this respect.
EDIT: it’s also comes off like, oh no one silly keystroke nuked my setup, but from an outside perspective, of course it did, it was a house of cards. I think a better framing would be that you dug a large hole for yourself by trying to force enterprise level complexity into a one-person project, and through sheer perseverance it somehow is still alive, but maybe some different architectural decisions early on could have avoided this.