The AI Kubernetes Show

The AI Kubernetes Show

The Kubernetes AI Show dives deep into the real-world challenges of adopting AI on Kubernetes platforms.

  1. Platform Engineering & Kubernetes: Guardrails For AI Code

    2D AGO

    Platform Engineering & Kubernetes: Guardrails For AI Code

    Learn how Schonfeld scaled their internal AI platform, SchonAI, using Kubernetes and established guardrails to manage AI agent code volume. Build your AI-native workflow now.

    54 min

  2. MAY 6

    One Dependency Away: Supply Chain Security in the Age of AI

    Secure your Kubernetes environment. Learn why zero trust cybersecurity is the only defense against AI agents and non-deterministic agentic software in your supply chain.

    50 min
  3. AI: Bubble or Bug? A CTO’s Perspective on Engineering in the AI Era

    JAN 14

    AI: Bubble or Bug? A CTO’s Perspective on Engineering in the AI Era

    Is the AI boom a bubble, or is it a new technological wave? Dinesh Majrekar, CTO of Civo, breaks down the current state of software development, explains why data sovereignty is the paramount security concern, and details how AI's real value lies in increasing code auality, not just velocity. In this episode of The AI Kubernetes Show, Civo CTO Dinesh Majrekar tackles the AI bubble hype, suggesting it is a blend of market speculation and genuine, disruptive innovation, drawing a comparison to the historical hardware monopoly of IBM during the mainframe era. He dives into the challenge of data sovereignty in the age of large language models, explaining Civo's solution of using an "on-prem public cloud" to run an OpenAI-compatible endpoint on private GPUs. This approach ensures maximum security for sensitive data, like medical records, by guaranteeing the data "never leaving your building." We also discussed the flattening curve of open source LLM capabilities, noting that models like the Kimi K2 model are now matching and even beating proprietary benchmarks while using fewer resources. Majrekar challenges the prevailing focus on speed, arguing the true value for software development teams is in boosting code quality. He champions code generation as the best AI use case but stresses it must be a "partnership" where saved time is reinvested in tackling technical debt and strengthening the code base. This is important for managing deployment risk. Finally, he addresses the dilemma of non-deterministic outputs in deterministic processes, which engineers simply call "a bug," emphasizing that AI is not a universal solution. Read the blog post: www.buoyant.io/ai-kubernetes-episode/ai-bubble-or-bug-a-ctos-perspective-on-engineering-in-the-ai-era Key Takeaways ✓ Code Quality is the true benefit of integrating AI; the time saved on initial generation should be used to fix technical debt and strengthen code. ✓ Achieving true Data Sovereignty requires running LLMs on private infrastructure (e.g., an on-prem public cloud) to keep data securely contained. ✓ The non-deterministic outputs of LLMs can be considered a "bug" in core engineering processes that demand algorithmic certainty. ✓ Code generation is the strongest AI use case, but developers must maintain ownership and set a high context standard for the LLM to follow. ✓ Open source LLM capabilities are now "on par" with proprietary models. Hit the like button and subscribe to The AI Kubernetes Show for more AI content!  What is your engineering team prioritizing with AI: velocity or quality? Let us know in the comments below! #AI #CodeQuality #DataSovereignty #SoftwareDevelopment #PlatformEngineering #Kubernetes #LLM

    27 min
  4. Moving from Single Agents to AI Agent Fleets

    JAN 14

    Moving from Single Agents to AI Agent Fleets

    The future of software development isn't about single agents—it's about building AI agent fleets! Dive into this conversation with Okteto CEO Ramiro Berrelleza to understand how this shift is fundamentally changing platform engineering and accelerating developer productivity.  In this episode of The AI Kubernetes Show, we sat down with Ramiro to discuss AI adoption and the need for constant experimentation in the current "Cambrian explosion" of AI tooling. Berrelleza highlights the move from single-threaded AI tools to large, asynchronous AI agent fleets, which solves the bottleneck of waiting for a single AI response. This agentic model is a game-changer, with some early adopters seeing a massive increase in output. Organizations need to adapt for AI-native workflows, because the focus on traditional metrics like measuring code production (lines of code, number of PRs) for AI is flawed. Instead, organizations should identify and focus their AI projects on their real constraints, such as slow CI workflows. Ramiro also addresses the disproportionate challenge of open source maintainer overload caused by AI-generated contributions, proposing a policy of "human-proof code." Finally, AI agents are presented as a powerful technical context multiplier for everyone from sales engineers to the CEO, significantly speeding up the onboarding process and improving communication across the organization.  Read the blog post:  Takeaways ✓ The future is moving from single-threaded AI tools to "AI agent fleets" to solve productivity bottlenecks. ✓ Traditional metrics like lines of code or PR count are now ineffective for measuring AI-driven developer productivity. ✓ The new focus for AI investment should be on organizational bottlenecks, such as optimizing slow CI workflows. ✓ Open source projects should adopt policies like "human-proof code" to manage maintainer overload from AI contributions. ✓ AI agents can serve as a technical context multiplier, speeding up onboarding and improving organization-wide understanding of complex code. Hit the like button, subscribe for more content on platform engineering and AI, and ring the notification bell.  What is the biggest productivity bottleneck you've solved with AI agents? Let us know in the comments! #AIAgentFleets #PlatformEngineering #DeveloperProductivity #Kubernetes #KubeCon #Okteto #AgenticAI #OpenSource #SoftwareDevelopment #TechTrends

    27 min
  5. Why Testing and Validation are the Unsolved AI Code Challenges

    JAN 14

    Why Testing and Validation are the Unsolved AI Code Challenges

    Is your engineering org ready for the speed of AI? Grant Miller, CEO of Replicated, breaks down the intersection of AI and platform engineering, revealing why testing and validation are the biggest unsolved problems in the industry. In this episode of The AI Kubernetes Show, we sit down with Replicated CEO Grant Miller to discuss how the pace of AI is fundamentally reshaping software development. Miller argues that engineering velocity has become the core competitive differentiator and shares the concept of "leadership empathy," where leaders contribute to a pull request with AI to understand the new tools. This increased velocity, however, puts significant system pressure on platform engineering teams, leading to "Frankenstein-y" application footprints and a greater need for top-notch observability and optimized CI/CD pipelines to improve "iteration speed total." The unique distribution challenges of self-hosted AI applications and the difficulty of validating AI code generation, especially for templated infrastructure-as-code like Helm charts and Terraform. Unlike front-end code, the human validation loop for infrastructure-as-code is not intuitive, making the complexity of testing and validation the industry's most significant hurdle. Read the blog post:  Takeaways ✓ AI turns engineering velocity into the ultimate competitive advantage, requiring organizations to move incredibly fast. ✓ Leaders must develop "leadership empathy" by using AI tools to understand the modern developer experience. ✓ Rapid AI code generation can lead to complex, "Frankenstein-y" application architectures, increasing pressure on platform engineering for troubleshooting and observability. ✓ The biggest challenge in AI-generated code is the lack of an intuitive validation loop for infrastructure-as-code like Helm charts. ✓ Testing and validation are the key unsolved problems and future areas for discovery and job creation. Liked this podcast? Hit the like button, subscribe for more AI and platform engineering insights, and let us know in the comments: What is the biggest challenge your team faces with AI-generated code? #AI #PlatformEngineering #EngineeringVelocity #AIGeneratedCode #TestingAndValidation #Kubernetes #Replicated #TechPodcast #CloudNative

    27 min

  6. JAN 7

    AI's Double-Edged Sword: The Technical Imperative and the Path to Accessibility

    Discover the dual nature of AI! Tech Lead Chris Khanoyan shares his view on the rapidly changing AI and data science landscape and the critical need for a technical foundation and the transformative power of AI accessibility for the deaf community.  In this episode of The AI Kubernetes Show, we dive deep into the world of AI and data science with Chris Khanoyan, a tech lead and senior data scientist at Booz Allen. Chris highlights the rapidly changing data science landscape, noting the significant overlap between data scientists and data engineers. While auto-generated code has made coding more accessible to practically anyone, he stresses that a solid technical foundation remains critical for debugging and understanding the fundamental elements of a system. We covered the foundational challenge of data governance and the need for clean, trustworthy data. Chris explains the importance of establishing a data pipeline and provenance (where the data comes from and who owns the dataset) before training any Large Language Models (LLMs). He offers a core principle for starting any project: begin with the end in mind. We also explore the hurdles of overcoming data access and scarcity, which often require formal agreements with non-technical clients, especially in sectors like the federal government. Finally, as a deaf individual, Chris provides a unique perspective on AI accessibility. He discusses how AI assistance is easing the mental fatigue from constantly processing captions and the potential game-changer of AI-powered glasses for live captions, while also addressing the current security and data sensitivity barriers that prevent their widespread adoption. Read the blog post: www.buoyant.io/ai-kubernetes-episode/ais-technical-imperative-and-the-path-to-accessibility Follow us on LinkedIn: https://www.linkedin.com/company/the-ai-kubernetes-show/ Takeaways ✓ A solid technical foundation is still vital for practitioners to manage bugs, even with the rise of AI code generation. ✓ Data governance and establishing data provenance are primary challenges in successful AI implementation. ✓ AI projects must always begin with the end in mind to effectively prepare and utilize data. ✓ Workarounds for data scarcity involve combining and consolidating various datasets from different systems (on-prem and cloud). ✓ AI accessibility tools, such as live captioning on glasses, offer a significant boost to productivity and ease mental fatigue, though data security remains a critical barrier. If you enjoyed this conversation on the technical imperative of AI, hit the Like button and subscribe for more expert interviews!  Let us know in the comments: What is the single biggest data governance challenge your team is facing today?  #AIandDataScience #DataGovernance #AIAccessibility #TechLeadInterview #DataProvenance #LLMData #GoogleCloud #DataEngineer #TechInterview #MachineLearning

    19 min

  7. JAN 7

    Maintaining DevOps Integrity in the Age of AI Velocity

    Is AI velocity breaking your DevOps processes? We sat down with Principal Platform Engineer Ahmed Bebars to discuss the critical balance of using AI to ship code faster while maintaining DevOps integrity in your platform engineering team. Ahmed Bebars, a principal platform engineer and CNCF ambassador, breaks down the AI's impact on SDLC and the transformation of platform engineering. In this The AI Kubernetes Show episode, he argues that AI is a powerful productivity tool that increases velocity, but teams must uphold established DevOps processes, including rigorous integration and regression testing, to prevent disruption and ensure quality. We discuss how Large Language Model (LLM) output is directly tied to input context, leading to the highly favored concept of spec-driven development, where humans guide the AI with precise specifications. The discussion also explores the challenge of adopting a new mindset for the non-deterministic nature of LLMs. Ahmed explains the difference between deterministic vs. non-deterministic LLMs and how tooling can be used to make the outputs predictable. For leaders looking at preparing platform engineering teams for AI, he advises embracing the technology, starting small, and focusing on hosting local LLMs and building agentic workflows for use cases like incident response triage and data gathering.  Read the blog post: www.buoyant.io/ai-kubernetes-episode/maintaining-devops-integrity-in-the-age-of-ai-velocity Follow us on LinkedIn: https://www.linkedin.com/company/the-ai-kubernetes-show/ Takeaways ✓ How to use AI to increase code velocity without compromising established DevOps processes. ✓ The critical role of context and spec-driven development for high-quality LLM output. ✓ Understanding the engineering mindset shift required to work with non-deterministic LLM outputs. ✓ Practical advice for preparing platform engineering teams for AI through local knowledge and agentic workflows. ✓ The broader role of AI in the development ecosystem, including documentation, testing, and observability. If you found this discussion valuable, please like this video, subscribe for more insights into The AI Kubernetes Show, and hit the notification bell!  What's the biggest challenge your team faces with integrating AI into your SDLC? Let us know in the comments below!  #AI #DevOps #Kubernetes #PlatformEngineering #SDLC #SpecDrivenDevelopment #CNCF #KubeCon #TechTalk #OpenSource

    27 min

  8. JAN 7

    The AI Tug-of-War: Bridging the Divide Between Platform Engineering and Data Science

    Keith Maddox, co-lead of the Kubernetes AI Working Group, breaks down the architectural shifts and security challenges required to run enterprise AI agents at scale. In this The Kubernetes AI Show episode, we chat with Keith Maddox, senior principal software engineer lead at Microsoft and Istio maintainer, who shares his perspective on the convergence of data science, AI agents, and platform engineering on Kubernetes AI workflows. He details the organizational dissonance between traditional platform stacks and data science workflows and how the Kubernetes AI working group is working to create a seamless migration path. We cover advanced model specialization techniques like Low Rank Adaptation (LoRA) and Retrieval-Augmented Generation (RAG), which are crucial for enterprise use cases driven by data privacy and liability concerns. Maddox also provides advice for platform owners, including the technical and non-technical strategies for LLM token spend management—recommending an egress gateway to centralize policy—and the importance of customer empathy with application developers. A major focus is the AI agent identity security gap, which falls between traditional human and machine identities. He strongly advocates for a zero trust AI mindset and immediate mitigation through agent sandboxing (using technologies like gVisor, KVM, or Wazet) and short-lived, ephemeral machine identities to manage the non-deterministic nature of LLMs. Read the blog post: www.buoyant.io/ai-kubernetes-episode/the-ai-tug-of-war-bridging-the-divide-between-platform-engineering-and-data-science  Follow us on LinkedIn: https://www.linkedin.com/company/the-ai-kubernetes-show/  Key Learnings ✓ The core conflict is a "tug of war" over tech stacks between platform and data science teams. ✓ Model specialization is necessary due to the high cost and lack of specificity of foundational models for enterprise applications. ✓ Managing LLM costs requires centralizing policy through an egress gateway and open communication with development teams. ✓ AI agents pose a new security challenge, requiring a move toward short-lived, ephemeral machine identities and agent sandboxing. ✓ A "Zero Trust" mindset is the recommended security approach for non-deterministic AI agents and workflows. If you're building, deploying, or securing AI workflows, hit the Like button and subscribe for more deep-dive technical content!  Let us know in the comments: What is the biggest challenge your team is facing with AI agent identity and security today?  #PlatformEngineering #Kubernetes #AIAgents #LLMs #ZeroTrustAI #KubeCon #DataScience #TechSecurity #DevOps

    26 min
See All (21)

Ratings & Reviews

5
out of 5
2 Ratings

About

The Kubernetes AI Show dives deep into the real-world challenges of adopting AI on Kubernetes platforms.

Information

  • Creator
    The AI Kubernetes Show
  • Years Active
    2K
  • Episodes
    21
  • Rating
    Clean
  • Copyright
    © The AI Kubernetes Show
  • Show Website
    The AI Kubernetes Show