Discover and read the best of Twitter Threads about #makeK8sBoring
Most recents (1)
k8s folks alway say "infrastructure should be boring", but we spend a lot of time on fancy non-boring stuff, like (eg) horizontal pod autoscaling.
So here's a counterfactual thread: what if k8s WAS boring?
What if `kubectl` proactively told you how your deployment was going?
So here's a counterfactual thread: what if k8s WAS boring?
What if `kubectl` proactively told you how your deployment was going?
What if `kubectl` proactively gave you specific, information about what caused your deployment to fail? What if that information DID NOT require wiring up complex monitoring services or buying some SaaS? 
What if `kubectl` allowed you to easily inspect JSON diffs (rather than text diffs) of every change you made to your config code, and got a specific breakdown of how that change cascades through the kube resources in your app?
