Joe Thompson's experience with Kubernetes began in early 2015 with a single-node lab install in a Red Hat training class. Since then he's delivered training, contributed to Helm, spoken at KubeCon and Cloud Native Rejekts several times, and given talks at local meetup groups -- all while delivering Kubernetes solutions in the real world for a variety of end users and vendors including CoreOS, Capital One and D2iQ. Now at HashiCorp, Joe continues working with Kubernetes both personally as a practitioner and community participant, and professionally as a HashiCorp solutions engineer advising customers and prospects on (among other things) using the HashiCorp stack with Kubernetes.
Avoid Spikes: Unexpected Kubernetes Behaviors
We all know that Kubernetes is complex and provides an ever-increasing set of capabilities for managing your workloads, but the basics of it like how pods work, how you expose a service, and so on are pretty simple... or are they? Even basic operations occasionally have sharp edges that can give you nasty papercuts deploying your apps because what you might intuitively assume to be the case, isn't how Kubernetes actually works. Joe Thompson takes you through some of these "you'd think that, but..." cases, details how Kubernetes "thinks" about them, and offers advice on how you can mitigate or change Kubernetes' behavior so that those papercuts don't become grievous wounds in your workloads or the clusters running them.