|
|
|
|
|
|
by Eritico
1580 days ago
|
|
|
I actually believe that the k8s api could be the best abstraction for services we ever had. While i'm running k3s at home (which is very nice to be honest) and big instances at work, i would prefer to have more managed k8s offerings but many already exist. They exist from DigitalOcean, Google, Azure, AWS and its probably way easier for smaller service providers to make a managed solution available. You can also use rancher or gardener to create and manage k8s clusters 'raw' by yourself. |
|
|
Even for tiny personal deployments, I find it a very compelling experience (I'm running micro-k8s at home).
With just a little bit of setup (configuring NAS storage, handing MetalLB an ip range, and installing cert-manager) I get a setup that is robust to any single machine failure (I run a 3 node system on old desktops/laptops), handles a bunch of previously manual tasks (backups, cert updates, auto-restarts) and gives me a wonderful host of tools I now use for personal projects, such as
- CI/CD (DroneCi)
- Private docker registry (Registry:2)
- Dashboard for service availability (kubernetesui/dashboard)
- A TON of personal hosted projects and tools (from bookstack to jellyfin to whatever project I'm working on now)
And for the most part - I just don't have to think about it all that much. Sure, the initial setup took a few hours. But I've torn down and rebuilt the entire thing from scratch in less than an hour from backups, and my README for "starting with nothing but a blank disk in an old machine to fully functional" is about 2 pages long, and the vast majority of it is local router config and DNS entries (still manual).
I'm easily replacing hundreds of dollars a month in SaaS/Cloud charges with it, and it's still just not taking up all that much of my time.