Uploaded May 2026 | Updated September 2026, 1 day ago
In this AMA livestream, Viktor is joined by regular guest Scott and special guest Brett Fisher to tackle a wide range of DevOps and AI-related questions. Brett opens with a discussion about his Agentic DevOps Guild — a membership community focused on just-in-time learning for DevOps and platform engineers navigating the rapidly evolving AI landscape, covering tools like Claude Code, Cursor, GitHub Copilot, and open-source alternatives like OpenCode. The conversation explores how to integrate AI into SRE workflows, the importance of prompt engineering, vector databases, and RAG for reducing hallucinations, as well as the challenge of building agentic automation incrementally rather than expecting overnight transformation.
The group also digs into practical topics including Crossplane V2 migration experiences, best practices for managing Argo CD at scale (with Scott predictably advocating for Flux), and whether kubeadm clusters can be reasonably secured. A lively discussion around vibe coding and non-engineer developers using AI tools like Claude's cloud co-work raises questions about how platform engineers should adapt their internal developer platforms — touching on Backstage, Crossplane, MCP servers, and agent skills as key building blocks. The episode wraps with a debate on the best strategies for distributing and versioning AI skills across teams, with Viktor and Scott making a strong case for remote MCP servers as the most scalable and standards-aligned solution.
▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Intro (skip to first question)
15:19 Should DevOps engineers learn development work?
19:32 Crossplane V2 migration experience and challenges
22:14 Recommendations for MCP server gateways
26:00 How to integrate AI as an SRE without hallucinations
36:35 How to secure a kubeadm cluster
38:39 How should DevOps prepare for non-engineers as customers (vibe coding)?
50:47 Best practices for Argo CD at scale (1000+ apps)
57:45 Self-service platform for non-engineers that isn't Heroku
01:10:33 How to propagate new skill versions across a team
In this AMA livestream, Viktor is joined by regular guest Scott and special guest Brett Fisher to tackle a wide range of DevOps and AI-related questions. Brett opens with a discussion about his Agentic DevOps Guild — a membership community focused on just-in-time learning for DevOps and platform engineers navigating the rapidly evolving AI landscape, covering tools like Claude Code, Cursor, GitHub Copilot, and open-source alternatives like OpenCode. The conversation explores how to integrate AI into SRE workflows, the importance of prompt engineering, vector databases, and RAG for reducing hallucinations, as well as the challenge of building agentic automation incrementally rather than expecting overnight transformation.
The group also digs into practical topics including Crossplane V2 migration experiences, best practices for managing Argo CD at scale (with Scott predictably advocating for Flux), and whether kubeadm clusters can be reasonably secured. A lively discussion around vibe coding and non-engineer developers using AI tools like Claude's cloud co-work raises questions about how platform engineers should adapt their internal developer platforms — touching on Backstage, Crossplane, MCP servers, and agent skills as key building blocks. The episode wraps with a debate on the best strategies for distributing and versioning AI skills across teams, with Viktor and Scott making a strong case for remote MCP servers as the most scalable and standards-aligned solution.
▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Intro (skip to first question)
15:19 Should DevOps engineers learn development work?
19:32 Crossplane V2 migration experience and challenges
22:14 Recommendations for MCP server gateways
26:00 How to integrate AI as an SRE without hallucinations
36:35 How to secure a kubeadm cluster
38:39 How should DevOps prepare for non-engineers as customers (vibe coding)?
50:47 Best practices for Argo CD at scale (1000+ apps)
57:45 Self-service platform for non-engineers that isn't Heroku
01:10:33 How to propagate new skill versions across a team
