Velero backup (didn't work)

It didn't work. Turns out there is a open PR that fixes some AWS API checksum issue that I did not take time to fully understand. I tried with both Backblaze B2 and Cloudflare R2. But I suppose I would have to wait until the AWS upload plugin works. I was very happy to see how well designed Velero is

This is one observation I made when developing with LLMs, is that I don't neccessarily take the time to understand what exactly is the problem. If it vaguely makes sense, I take it as the truth. And it might as well be, if my experience serves any purpose, but I can not be 100% certain. After I realised that backups won't work this evening, I started cleaning up some of the unused applications that weren't being used.

The cleanup was somewhat satisfying after a slightly disappointing evening. But in terms of my personal IT infrastructure, I am feeling a little bit overwhelmed. I realised I have to have a checklist to properly clean up everything related to each deployment, from secrets to DNS. And it takes quite a bit of time and mental effort to clean everything up properly, I don't really want things dangling around. Checklists might help, but I am wondering if I have truly bit more than I can chew in terms of what can be considered a "personal" cloud infrastructure. I would love have my IT infrastructure baggage free, but it seems to be that I am walking on the opposite direction, sadly.

I would be lying if I said that I hadn't considered going back to hosted blogging solution, while blogging is the only true use case for me. And currently I have a backlog of tasks that's probably longer than my backlog at work.

Anyway, here's a woodpecker.

#devlog #infra #it #journal #software