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. 2日前

    Treat Testing as a Platform Service on Kubernetes

    Most testing tools bolt onto a CI pipeline and hope for the best. Ole Lensmar, CTO of Testkube, built a company that changes that script. Pull test execution out of CI/CD entirely and run tests as Kubernetes workloads instead. In this episode, Lensmar walks through why Testkube uses Kubernetes as its test execution engine, running Selenium, Playwright, K6, JMeter, and Postman tests as cluster workloads instead of asking teams to adopt new tools. He and podcast host William Morgan dig into who should own testing (developers own functional tests,  while the platform team owns performance, security, and chaos testing). Lensmar's core recommendation is to treat testing and quality as a platform capability, the same way you already treat CI and CD.  More AI-generated code means more tests are needed, intelligent test selection can keep pipelines fast as test counts grow, and AI is already useful for triaging failed test logs using Kubernetes and Grafana MCP servers.   TAKEAWAYS:  ✓ Where testing ownership splits between developers and the platform team, and where it doesn't  ✓ Why "testing as a platform service" should get the same priority as CI and CD  ✓ How intelligent test selection works, and why you should never rely on it alone  ✓ Where AI already adds value today: triaging failed test logs with Kubernetes and Grafana MCP servers  ✓ Why testing the AI components of your application (agents, evals) is becoming its own discipline. Read the blog post at:

    Treat Testing as a Platform Service on Kubernetes
  2. 1月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

    AI: Bubble or Bug? A CTO’s Perspective on Engineering in the AI Era
  3. 1月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

    Moving from Single Agents to AI Agent Fleets

番組について

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