Kubernetes Best Practices 101
tl;dr: “Purpose of this guide is to help with the learning curve, helping to prepare a more stable, reliable and functional environment."
featured in #252
Why You Should Build On Kubernetes From Day One
tl;dr: It took a to get up: "provision virtual machines, install, configure, configure, configure." Once the cluster was up, "Kubernetes was great for us—but we wanted somebody else to run it." Max founds three benefits: (1) Managed Kubernetes does the heavy lifting. (2) You can mostly stay cloud agnostic. (3) Easily spin up new environments.
featured in #242
No, We Don’t Use Kubernetes
tl;dr: Maik is commonly asked by customers and interviews if they use Kubernetes as their primary dev platform. He believes the tech is "still very much at the peak of its hype cycle" and details a cost-benefit analysis of it in this post.
featured in #240
Why Does Developing on Kubernetes Suck?
tl;dr: (1) Myriad dev environments (2) Permissions & authentication issues (3) Network debugging (4) Logging into a container and doing ttuff, and more....
featured in #151
The Business Executive's Guide to Kubernetes
tl;dr: Some of the weak points of Kubernetes - it's not to be used for stateful data, often the control dashboard is unsecured leading to vulnerability, consistent issues around upgrading, and others. "With the good, comes the bad".
featured in #149
Tinder’s Move To Kubernetes
tl;dr: Two year migration so that Tinder can run exclusively on a Kubernetes cluster consisting of 200 services, 1,000 nodes, 15,000 pods, and 48,000 running containers.
Click the link in this tweet if paywalled.
featured in #140