What Happens After the POC: Building Agentic Systems That Last
summary
InfraAssistant is a Kubernetes microservice hooked to Slack that starts as a simple RAG over internal docs and scales into a dynamic multi‑agent system using Bedrock then full MCP support, a tool lake of hundreds of tools, and a brain agent that spawns lightweight sub‑agents on demand. It indexes ~1,000 repos (S3/vector backend), runs AWS CLI in isolated read‑only envs, and solves real infra tasks (one troubleshooting run takes 8–10 minutes). It is open source as Infra Kitchen but is pulled from org‑wide use after a GitHub token granted unintended repo write/branch‑override power.
AI-written summary · about
chapters (12)
- 0:00Agentic systems at Electrolux
- 3:20Platform team challenges
- 4:24Agentic journey start
- 8:38Tools and access management
- 11:05Scaling with multi-agent
- 14:13Rewriting evolving systems
- 16:18MCP for tool integration
- 19:04Dynamic sub-agent spawning
- 21:34Infra Kitchen provisioning
- 25:55Lessons from agentic systems
- 31:15Why system shutdown
- 34:44Future plans & Q&A
related talks
34mAutomating SRE Operations with Multi-Agent AI
36mPutting AI Agents to Work: A New Era of Open Source Connectivity with MCP
40mAgents in Action: Advancing Open Source AI Missions
36mAI's Disruption of Infrastructure Operations
38mBuilding AI Agents and Assistants for DevOps Workflows
19mBuilding Agents at Cloud Scale
16mWhat Comes After AI Coding Assistants
32mFrom Toil To Triumph: Harnessing Agentic AI To Streamline Infrastructure as Code