I see a lot of people having problems to understand how the Kubernetes platform works at the fundamental level, e.g. resiliency and behavior. If you start thinking about Kubernetes as a fully event-driven system, there's answers to so many "Why"'s

If you're like me, you might (mis)use Twitter's Like button as a way to bookmark important tweets. Once you've reached several hundred or thousands of bookmarks, ehm Likes, it becomes really hard to find what you're looking for. Mainly because Twitter Likes are not designed for this type of use and the twitter.com UI search is not super flexible. However, with some CLI magic, we can easily fix that :)

During a recent customer engagement, a discussion about Kubernetes `NodeSelectors` came up. There was some confusion about whether and how to use them for a multi-tenant cluster deployment. In the end, we decided to leverage the Kubernetes `PodNodeSelector` admission controller.

Follow me into the rabbit hole to explore how does it look like inside Docker's "FROM scratch"

Answering a customer question about why "Allocatable" resources (CPU, MEM) on the Kubelet would not be reduced when he starts pods with QoS guarantees. This is a deep dive in the Kubernetes scheduler...