A year in, Google wants its Axion processors to feel like a scheduling decision
About this episode
The episode discusses Google's Axion processors and their viability for Kubernetes workloads after a year of production use.
At KubeCon Europe, Google Cloud’s Jago Macleod and Abdel Sghiouar argued that adopting Arm for Kubernetes workloads has shifted from a complex migration to a practical, low-friction choice. After a year of production use, Google’s custom Arm-based Axion processors—powering C4A and N4A instances—are positioned as broadly viable for most containerized applications, offering strong gains in performance, cost efficiency, and energy usage compared to x86.
More episodes of The New Stack Podcast
- Why Broadcom gave Velero to the CNCF Sandbox — and what it means for Kubernetes data protection
- Why AI engineering needs old-school discipline
- Jim Bugwadia on why finding a Kubernetes problem is only half the battle for Kyverno users
- How AWS Bedrock is shaping Model Context Protocol
- Why Microsoft is betting on temporary identities to stop autonomous agents from going rogue
- As agentic AI explodes, Amazon doubles down on MCP
Explore listener stats, chart rankings, contacts and more on the The New Stack Podcast podcast page.