I think @dbsmasher is asking me to explain kube on *my* laptop, so here we go...
It's critically important to treat computers as cattle, not pets. That's why setting up my laptop is a bespoke work of art roughly akin effort-wise to painting the ceiling of the Sistine Chapel.
FOUR WEEKS LATER, great. We're ready to install k8s!
FOUR WEEKS LATER, great. We're ready to install k8s!
Kubernetes and containers started on laptops. "How do I make my Mac with a busted keyboard look like a Linux server with no keyboard" is the question of the ages.
"Works on my machine" from developers was met with "well back up your email shithead, because your laptop's going to production" from sysadmins.
Docker Docker Docker solved all of this with a solution everyone can hate.
Docker Docker Docker solved all of this with a solution everyone can hate.
But there was a problem! If you run your workload inside of a container, you know where that container is running at any given time. That's unacceptable, so Google invented Kubernetes to combine their two favorite things: nondeterminism and being condescending to everyone.
Now we have the Development Best Practice: taking all of the various datacenter scale orchestration systems and collapsing them down to run on a single laptop.
It should be obvious by now that between this model and Chrome, Google is a front for Big RAM.
It should be obvious by now that between this model and Chrome, Google is a front for Big RAM.
Now thanks to the miracle of Kubernetes on My Laptop, I can spend all of my time dicking around with making my laptop work properly instead of writing code.
Given the quality of my code, this is a net positive for everyone.
Given the quality of my code, this is a net positive for everyone.
