Over the last few years I have been a big fan of minikube for getting a Kubernetes cluster up and running on the device I am working on, one of the biggest advantages was the addons available which meant it was an easy emulation of storage for K10 to be installed and start protecting some demo applications….
But minikube is broken!
I documented some fixes here…..
The benefits of using minikube or KinD (Kubernetes in Docker) or even K3s with rancher is that you do not really need to understand the underpinning technology, think of it a little like vSphere going back to pre ESX 3.5 days when you might have needed to interact with the CLI of your ESX hosts but these days less and less do we have to…
These local development clusters (even though we are not using them for development is a great way to get started learning about the higher level of applications running on Kubernetes without knowing the engine…. but we can still drive the vehicle.
Project Pace is one of my repositories for getting started with some scenarios. With the above fix, we can still work through this.
I wonder how many screenshots of people getting their first minikube cluster up and running we can get below?
