<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>DevOps on Corrupted Glitch</title>
		<link>https://corruptedglitch.netlify.app/categories/devops/</link>
		<description>Recent content in DevOps on Corrupted Glitch</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 18 Jul 2026 23:13:02 -0400</lastBuildDate>
		
			<atom:link href="https://corruptedglitch.netlify.app/categories/devops/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Automating the Great Escape: Cloud Migration Pipelines with an AI Copilot in the Loop</title>
				<link>https://corruptedglitch.netlify.app/posts/sample-devops-migration/</link>
				<pubDate>Tue, 14 Jul 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/sample-devops-migration/</guid>
				<description>&lt;p&gt;Every datacenter exit starts the same way: someone opens a spreadsheet with 1,400 rows, and someone else says &amp;ldquo;we&amp;rsquo;ll just lift and shift.&amp;rdquo; Eighteen months later, half the estate is still on-prem and the spreadsheet has become sentient.&lt;/p&gt;&#xA;&lt;p&gt;This is a field report from a migration that didn&amp;rsquo;t go that way — 140 production workloads moved in 11 months, zero rollback events. The difference wasn&amp;rsquo;t heroics. It was treating the migration as a &lt;strong&gt;factory&lt;/strong&gt;, not a project, and putting an AI copilot inside the loop where humans were the bottleneck.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The DevOps Home Lab: A Production Mindset on a Power Strip</title>
				<link>https://corruptedglitch.netlify.app/posts/devops-home-lab/</link>
				<pubDate>Tue, 21 Apr 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/devops-home-lab/</guid>
				<description>&lt;p&gt;A home lab is only useful if it teaches you habits that transfer to production. A pile of Raspberry Pis running hand-configured containers teaches you how to hand-configure containers. This guide builds the opposite: a small estate you operate &lt;em&gt;like an SRE&lt;/em&gt;, because the operating model — not the hardware — is the thing you&amp;rsquo;re practicing.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Project 03: Shifting Security Left with SAST in Azure Pipelines</title>
				<link>https://corruptedglitch.netlify.app/projects/project-03-shift-left-sast/</link>
				<pubDate>Fri, 10 Apr 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/projects/project-03-shift-left-sast/</guid>
				<description>&lt;p&gt;The mission: recurring vulnerability assessment across C# and TypeScript codebases, enforced automatically — a PR with a new critical finding cannot merge. No security review meetings, no spreadsheets.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Project 04: Kubernetes Autoscaling &amp; the EFK Observability Stack</title>
				<link>https://corruptedglitch.netlify.app/projects/project-04-k8s-autoscaling-efk/</link>
				<pubDate>Thu, 05 Mar 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/projects/project-04-k8s-autoscaling-efk/</guid>
				<description>&lt;p&gt;The mission: stop paying for idle pods and stop debugging production by &lt;code&gt;kubectl logs&lt;/code&gt;-ing one pod at a time. Two builds, one outcome: a cluster that scales itself and explains itself.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
