<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Sre on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/ai-sre/</link><description>Recent content in Ai-Sre on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 15:46:15 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/ai-sre/index.xml" rel="self" type="application/rss+xml"/><item><title>AI SRE evaluation: coding agents already have K8s context</title><link>https://curadevops.metacog.co.kr/insights/2026-10-21-before-you-evaluate-an-ai-sre-give-your-existing-agent-conte/</link><pubDate>Wed, 21 Oct 2026 15:46:15 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-21-before-you-evaluate-an-ai-sre-give-your-existing-agent-conte/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Offers a reframing worth absorbing before committing budget to a dedicated AI SRE product: existing coding agents may cover meaningful incident-investigation use cases with added context, no action required today.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Relevant to build-vs-buy decisions around AI SRE tooling; suggests evaluating what existing coding-agent licenses already cover before signing a dedicated AI SRE contract.&lt;/li>
&lt;/ul></description></item></channel></rss>