Vagrant Begone!

It's been a long time coming but still is a hard transition to be giving up using Vagrant as my go to tool as a sandbox for system design ideas.  I've got years of familiarity with it and more importantly, the mythos around it's creation called to me.  

Here is some of the backstory that I'm referring to:

But Vagrant is getting long in the tooth.  Many of the plugins for Vagrant are no longer maintained.  Hashicorp hasn't been devoting a lot of horsepower to developing Vagrant beyond minimal bug fixes and some re-architecting for longterm maintenance. I had held out hope that IBM buying Hashicorp would trigger Vagrant's renesaince but that was me completely not understanding what made Hashicorp valuable to IBM.  (Damn it, why doesn't the multi-billion dollar company not hold the same values that I do?!?!?!)

 Blah, blah, blah....  Lots of mourning and explaining why since it feels like I'm betraying a fellow traveller.  This probably speaks more to my attachment to things than I realize.  But that's something to take up with a therapist and not yet something ready for blogging.  The end result is that I've got to figure out what's going to replace this gap in my toolchest.  Not just at work but also in my side hustles.  For now it looks like I'm starting down the path of K8's and containers.  The beginning looks to be something like this.

brew install --cask docker
brew install k3d
brew install kubectl
brew install helm

And I know I'm late to the party....  Others have definitely made this transition well before me.  My day job is at an enterprise scale role.  Systems that have lifespans of decades.  Modernization takes time to occur when working systems have inertia on their side.  For me this is a bit of a leap since much of the technologies I have to work with don't even understand the concept of running on a seperate unix server from 100's of other applications in the ecosystem of applications in our environment.  One big happy bunch of apps all running on a single server with no boundary enforcement other than conventions and learned behavior.  Or to twist Shakesphere's words.  The good that developers do dies with their employment.  The bad becomes near immutable tech debt.