Submitted 6 months ago by georift@piefed.social to selfhosted@lemmy.world
Wondered if folks had a preferred method for implementing a GitOps approach for homelabs consisting of mostly docker compose stacks.
We run Kubernetes at work, and I’m tempted to migrate to that as it provides a slew of great GitOps tools, but I’ve been putting off that migration as I haven’t had the time to invest.
Is learning Ansible and going that route still the way to go?
Wondering, Just after how many containers does ops make sense? I have a dozen containers, I check for updates once a month manually. I update the compose/docker files manually and up my containers. In stages, because my git and my container registry are also containers. Also my dev is my prod env.
If feel like, for me at least, GitOps for containers is peace of mind. I run a small Kubernetes cluster as my home lab, and all the configs are in git. If need be, I know (because i tested it) if something happens to the cluster and I lose it all, I can spin up a new cluster and apply the configs from git and be back up and running. Because I do deployments directly from git, I know that everything in git is up to date and versioned so i can roll back.
I previously ran a set of docker containers with compose and then swarm, and I always worried something wouldn’t be recoverable. Adding GitOps here reduced my “What If?” Quotient tremendously.
How many hosts do you manage? What k8 tools do you use? I have just one host, I use bind mounts for container generated config/data/cache in docker compose, for which I dont have backup, and if gone, I have to start from scratch. But i try to keep most config in git.
I think it depends on the rate of change, rather than the amount of containers.
At home I do things manually as things change maybe 3 or 4 times a year.
Professionally I usually do setup automated devops because updates and deployments happen almost daily.
At one of my clients I use gitlab CI with ansible. It took 3 days to setup, and requires thinkering. But all in all, I like the versitility, consistency and transparency of this approach.
If I’d start over again, I’d use pyinfra instead of ansible, but that’s a minor difference.
That’s what I’m currently implementing. Here’s a cool guide: nickcunningh.am/…/how-to-automate-version-updates…
beeng@discuss.tchncs.de 6 months ago
K3s with flux inside. Fun video from a guy with a nice easy repo from goto conference on YouTube. Might be a bit much but… Not sure of anything for compose and gitops