The gap between Minikube and Kubernetes in production is vast and full of pain. Want to know what it’s like to implement Kubernetes (k8s) in production for the first time before you collect the bumps and bruises yourself? Join me to learn about the ups and downs of one company’s initial experience with k8s - including who was involved, the scope, and what was intentionally deferred.

We will cover:

• Why even consider Kubernetes (Hint: you might not benefit from it!)
• How a real company approached their first proof-of-concept
• How goals changed during implementation of k8s
• What we learned so far
• What we still need to learn

When I built and posted some content on my site today using Hugo v0.53, I found that I had unintentionally broken some permanent links I was proud of. Thankfully, Hugo has a built-in feature - aliases - to address this issue.

In October I was fortunate to be invited by Bryan Hogan to join him to talk about data science on the No Dogma Podcast. That episode posted in November. It was a really good time. :)

As I prepared to present the four previous posts (part 1, part 2, part 3, part 4) as “Dissecting Kubernetes” at KCDC X, I tried to upgrade from v1.9 to v1.11 of Kubernetes and I found that when we only have the kubelet and the kube-apiserver we run into a permissions issue we didn’t have before.

This is part 4 in a series of posts related to Kubernetes. Pervious posts were about kubelet, Kubernetes API, etcd, and kubectl, and kube-scheduler. This time we will explore kube-controller-manager and its role in managing replication of pods (a.k.a. scaling).