![]() The problem comes when you want to run code/Kubernetes configs on multiple of these clusters because they each have their own… let’s call them quirks. Instead of having to go out to the network to talk to a big Kubernetes cluster (that might be interacting with production data) you can spin up a small cluster on your laptop to check things out. In other words: they’re Kubernetes, but on your laptop. All of these are local Kubernetes environments. Minikube, MicroK8s, Docker for Mac, KIND, the list kind of goes on. So, how does developing on Kubernetes suck? Let me count the ways. ![]() When there’s another tool that solves a problem better than Tilt, I’ll use that. ![]() ![]() Full disclosure: While I work on Tilt as part of my job, which we have designed to solve some of these problems, another part of my job is writing software that runs on Kubernetes. In this post I want to walk through all of the problems I have encountered developing software on Kubernetes. When I’m writing software, though, Kuberentes has only made things harder. All told I’m happier operating a microservices app today than I was before I started using Kubernetes. Whole classes of production problems have disappeared–arguably to be replaced by others. Kubernetes has changed the way I operate software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |