libvirt-k8s-provisioner VS batect

(https://github.com/kubealex/libvirt-k8s-provisioner)

https://github.com/kubealex/libvirt-k8s-provisioner - A nice and easy to use kubernetes provisioner (both single node and HA) made with Ansible and Terraform!

It doesn't have everything out of the box, but keep your eyes on https://github.com/kubealex/libvirt-k8s-provisioner, it is fast growing and will include soon ci/cd tools and registry, plus rook and some other cool stuff.

https://batect.dev/ this is like Act but agnostic and public

If you're dockerizing a dev environment check out batect, it's kind of like the combo of docker-compose + make (i.e. simple script running) that is really the tool we all just want: https://batect.dev/ It can easily define one-off container tasks like integration test runs with just a couple lines of config.

Earlier this year at $DAYJOB I was on a project to uplift the deployment pipelines and DevOps capabilities within the team. Today we have full Continuous Deployment, Trunk Based Development, and SlackOps. I've written a couple of articles below on the approach we took which was around heavy use of Docker and the tool Batect.

Go the next step and run a local kubernetes cluster with kind or k3s (it will take you 30 seconds to have a k8s cluster going). IMHO the kubectl CLI is a lot more logical than docker's CLI. You can create all your local storage volumes ahead of time, create a pod that attaches to it, and then just kubectl exec into the pod vs. writing a long fiddly docker command line string (or crafting a docker-compose.yml). It's easy to adjust the pod as necessary while it runs too, like adding a service to expose ports without rerunning the container.

But if you do like the idea of docker dev environemnts, check out a tool like batect: https://github.com/batect/batect It's somewhat like if docker-compose had make-like commands you could define. Your whole dev environment and workflow can be defined in a simple yaml config that anyone can use.