If you're trying to make sense of when to use Kubernetes and when to avoid it, this episode offers a practical perspective based on real-world experience running production workloads.

Paul Butler, founder of Jamsocket, discusses how to identify necessary vs unnecessary complexity in Kubernetes and explains how his team successfully runs production workloads by being selective about which features they use.

You will learn:

  • The three compelling reasons to use Kubernetes are managing multiple services across machines, defining infrastructure as code, and leveraging built-in redundancy.

  • Why to be cautious with features like CRDs, StatefulSets, and Helm and how to evaluate if you really need them.

  • How to stay on the "happy path" in Kubernetes by focusing on stable and simple resources like Deployments, Services, and ConfigMaps.

  • When to consider alternatives like Google Cloud Run for simpler deployments that don't need the full complexity of Kubernetes

Sponsor

This episode is sponsored by Syntasso, the creators of Kratix, a framework for building composable internal developer platforms

More info

Rss Apple Podcaster
Podden och tillhörande omslagsbild på den här sidan tillhör KubeFM. Innehållet i podden är skapat av KubeFM och inte av, eller tillsammans med, Poddtoppen.