since i am using docker-compose locally, i have little use for vagrant nowadays. For staging and production the docker containers run inside a Kubernetes environment which i don't want to replicate locally. Am i missing something ?
It seemed like a pretty legitimate question: is there a compelling reason to give Vagrant 2 a look if Docker/Kubernetes is your current workflow? It seems to me you took it as more of an us-vs-them comment.
You probably wouldn't look at Vagrant if you are using Docker/Kubernetes. Vagrant (virtual machines) and Docker (containers) fill different niches. If you can accomplish your work with containers then you don't need to manage virtual machines.
We have had a number of people want to replicate locally for offline use cases (train/plane), reduced bandwidth use cases (home/plane/train), and cost reasons (laptop VMs are always cheaper than cloud). If you like Vagrant and Kubernetes checkout the Tectonic Sandbox[1] or if you don't want to use vagrant checkout minikube[2]. We (CoreOS) invested time into both projects for these reasons.
I think you're correct. There's no reason to use vagrant. It's self titled as a way to do dev environments. You don't want dev environments. You just want config management. Like ansible or salt. I don't see why you don't want a dev environment tho. It's nice being able to code while on a train or a flight.
