Podcast profile
By KubeFM
Discover all the great things happening in the world of Kubernetes, learn (controversial) opinions from the experts and explore the successes (and failures) of running Kubernetes at scale.
Latest episode
28 min
Topics
Kubernetes architecture, operations, ecosystems, workloads, and cluster management.
Software delivery, infrastructure automation, CI/CD, collaboration, and operational practice.
Processors, memory, accelerators, systems architecture, and computing hardware design.
Formats
Detailed technical, architectural, or research-oriented examination.
Host-led conversation where a guest supplies most of the subject matter.
Audience level
Regularly assumes specialist knowledge and discusses implementation, architecture, protocols, code, or research in depth.
Stay connected
From the feed
Episodes shown — 10 of 25
Non-deterministic agents pose specific challenges for platform teams in observability, state management, governance, and trust. Mauricio (Salaboy) Salatino explains why agentic applications behave like distributed multi-agent systems.
KubeSelect is a new show that tests one bold Kubernetes hypothesis with one expert. Hosts Salman Iqbal and Bart Farrell examine the evidence and ask whether the claim holds up. In episode two, Kat Cosgrove tackles a long-running question: should teams run databases on Kubernetes?
Kube Select takes one bold Kubernetes hypothesis and tests it with an expert. In the first episode, Salman Iqbal and Bart Farrell ask whether most organizations have an observability problem or a decision-making problem. Henrik Rexed, Senior Staff Engineer at Dynatrace, challenges the original claim.
Kube Signals starts where the keynote ends: with the trends that platform teams will have to operationalize next. In this special episode, Brian Teller speaks with Saiyam Pathak about his KubeCon India keynote and the shift from developer platforms to AI factories.
At enterprise scale, a deployment pipeline that runs Helm upgrades directly against Kubernetes hides drift, mixes configuration with CI logic, and makes the last pipeline run the source of truth. Elad Cohen explains how WSC Sports moved from Azure DevOps to GitHub Actions and redesigned delivery around Git and Argo CD.
Karpenter can reduce Kubernetes infrastructure costs, but aggressive node consolidation can also expose workloads that lack disruption safeguards.
An unmaintained identity component can remain invisible until a routine Kubernetes upgrade turns it into an incident.
GPU inference throughput depends on more than accelerator generation or count. Memory bandwidth, model parallelism, cache configuration, and the load generator itself all influence measured throughput.
Forced platform migrations are usually treated as something to survive. At Scout24, a mandatory OS migration became an opportunity to rethink Kubernetes autoscaling, node provisioning, and infrastructure efficiency.
Most teams scale Kubernetes by thinking about pods and nodes. At Render, Brian Stack ran into a different dimension: hundreds of thousands of namespaces per cluster, multiplied across DaemonSets that list-watch every namespace.