How Zalando manages 140+ Kubernetes Clusters
Recently I was asked "how do you manage that many Kubernetes clusters?". This post tries to provide some insights on how we manage 140+ Kubernetes clusters on AWS at Zalando.
Liveness Probes are Dangerous
Kubernetes livenessProbe can be dangerous. I recommend to avoid them unless you have a clear use case and understand the consequences. This post looks at both Liveness and Readiness Probes and describes some "DOs" and "DON'Ts"
K3s, Traefik, Let's Encrypt, and Local Path
The story on how I messed up my K3s demo site with Traefik as Ingress controller and Let's Encrypt rate limits — or: how to configure K3s with local-path volumes.
Kubernetes and Python
While Go is the language-of-choice in the cloud-native world, Python has a huge community and makes it really easy to extend Kubernetes in only a few lines of code. This post is a follow-up to a talk I gave last week in Prague.
Kubernetes Web UIs in 2019
This post takes a look at different open source Kubernetes web UIs, my requirements, and why I created Kubernetes Web View to help with support and troubleshooting across multiple clusters.
Kubernetes on AMD64 with PC Engines APU2
I want to run Kubernetes on amd64 hardware. I already own two Raspberry PIs, but I always struggle with ARM and the need to create custom Docker images. This post explains how to run a single-node Kubernetes (K3s) on the PC Engines APU2 board with an embedded AMD CPU.
KubeCon Barcelona Recap
KubeCon EU happened in Barcelona this year (May 20 - 23). This is my personal conference recap. I will not talk about any of the official KubeCon announcements (as there are enough other places to read about them).
Kubernetes Fails: 3 ways to kill your clusters
Kubernetes has its virtues and is worth investing in, but it is undoubtedly complex and comes with many operational challenges. We faced many of them on our journey towards "cloud native" at Zalando.
Many Kubernetes Clusters
As a reply to Zalando's "Running 80+ clusters in production" post, someone asked whether this (80+ clusters) would not defeat "the purpose"? My answer would not fit in a Tweet, so here it is as a blog post.
Accelerate: Software Delivery Performance
The Accelerate book is about "measuring software delivery performance — and what drives it — using four years of groundbreaking research and rigorous statistical methods". I'll try to explain why I see the book as a blueprint for platform teams and how it relates to developer experience.