3 ms·
Eh, people who don't know tf/ansible say these things because they don't know the tool. When you know the tool it's no big deal and it's preferred for repeatabi
by Notanothertoo 5y ago
Eh, people who don't know tf/ansible say these things because they don't know the tool. When you know the tool it's no big deal and it's preferred for repeatability and its self documenting. People often think it's just good for complex things but infra as code solves a lot of problems. I use tf for my home lab because that's what I'm failure with and a homelab will inevitably get tinkered with or fall out of state. Same reason I use tf for everything infra as a dev consultant of 1. I'm not going to touch this thing for a while and when I do I want it to be repeatable and documented so I can move forward instead of back.
Also kubernetes is easy when using the right spin up tool, like portainer or rancher. It's also the only way to run docker images across multiple machine today. For a while I ran swarm but that's dead, then I just used docker compose but started running into compatibility issues. With kube you also get to leverage all the existing helm charts., which saves a lot of time.
It's still a bit overkill but a lot of fun, and I learned networking and infra things doing it on a homelab. I also use it to try new things.
There are also political reasons to do so. I suspect the internet will get less free and it's nice having your own private space.
- selfhoster11 5y agoI agree with everything except for Kubernetes. My use of Ansible for example is purely so I don't forget what tweaks I made to the system to make things run.