Learning Kuberenetes is surprisingly difficult when all you have ever done is regular systems administration.
Even just jumping from docker-compose to k3s is quite a big step, and involves learning many concepts that don't have good analouges in previous experience.
I am currently in the proccess of moving more and more of my infrastructure to kubernetes,
hopefully this will clear up some resources and make my setup a bit more resilliant.
Most of it is running on old, used hardware. For example my old laptop that got me trough
two apprenticeships and is around 13 years old at this point.
The reason for this is that I don't like waste, and the laptop still works fine.
It just sitting there collecting dust, while perfectly capable of handling some tasks annoyed me.
This Post and this Website function as a test for this odd concept.
When I push a new revision of the site, it gets built with a forgejo-builderm, and pushed with the respective tag.
The result is a OCI container.
The kuberenetes cluster runs argocd, and this regularly checks the git for updates to the chart repo.
If I want to update the website, I commit the change, tag it, push it.
Then the builder vomits out the OCI container, pushes that to forgejo's builtin container registry.
In the meanwhile I update the chart to point to the new revision.
Argocd will pick up the change after a few minutes or whatever (I haven't figured out the schedule yet),
and then change the deployment accordingly.