KubeFM

Fabián Sellés Rosa, Tech Lead of the Runtime team at Adevinta, walks through a real engineering investigation that started with a simple request: allowing tenants to use third-party Kafka services. What seemed straightforward turned into a complex DNS resolution problem that required testing seven different approaches before a working solution was found.You will learn:Why Kafka's multi-step DNS resolution creates unique challenges in multi-tenant environments, where bootstrap servers and dynamic broker lists complicate standard DNS approachesThe iterative debugging process from Route 53 split DNS through Kubernetes native pod DNS config, custom DNS servers, Kafka proxies, and CoreDNS solutionsHow to implement the final solution using node-local DNS and CoreDNS templating with practical details including ndots configuration and Kyverno automationPlatform engineering evaluation criteria for assessing solutions based on maintainability, self-service capability, and evolvability in multi-tenant environmentsSponsorThis episode is sponsored by LearnKube — get started on your Kubernetes journey through comprehensive online, in-person or remote training.More infoFind all the links and info for this episode here: https://ku.bz/NsBZ-FwcJInterested in sponsoring an episode? Learn more.

Amos Wenger, a developer and writer specializing in hands-on Kubernetes experiences, shares his intriguing saga of adding a home computer to his production K3s cluster. He delves into how this decision led to TLS certificate renewal failures due to NAT issues with consumer routers. The conversation highlights debugging tools like K9s and netshoot, and the unexpected IPv6 behavior encountered. Amos offers best practices for managing mixed infrastructure and encourages listeners to avoid mixing home nodes with production for a smoother experience.

Tanat Lokejaroenlarb, an SRE at Adevinta leading the runtime team for the Ship platform, dives into his journey migrating to AWS Karpenter. He reveals how replacing EKS Managed Node Groups enhanced Kubernetes operations, cutting costs by €30,000 monthly. Tanat discusses innovative strategies like decoupling upgrades, implementing automated instance selection, and using Kyverno for policy automation. Learn about over-provisioning with low-priority pods and the significant performance benefits of AMD adoption. His insights are a must for anyone in cloud-native operations!

Festus Owumi walks through his project of building a lightweight version of Kubernetes in Go. He removed etcd (replacing it with in-memory storage), skipped containers entirely, dropped authentication, and focused purely on the control plane mechanics. Through this process, he demonstrates how the reconciliation loop, API server concurrency handling, and scheduling logic actually work at their most basic level.You will learn:How the reconciliation loop works - The core concept of desired state vs current state that drives all Kubernetes operationsWhy the API server is the gateway to etcd - How Kubernetes prevents race conditions using optimistic concurrency control and why centralized validation mattersWhat the scheduler actually does - Beyond simple round-robin assignment, understanding node affinity, resource requirements, and the complex scoring algorithms that determine pod placementThe complete pod lifecycle - Step-by-step walkthrough from kubectl command to running pod, showing how independent components work together like an orchestraSponsorThis episode is sponsored by StormForge by CloudBolt — automatically rightsize your Kubernetes workloads with ML-powered optimizationMore infoFind all the links and info for this episode here: https://ku.bz/pf5kK9lQFInterested in sponsoring an episode? Learn more.