<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Auto-Rollback on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/auto-rollback/</link><description>Recent content in Auto-Rollback on SRE Engineering Practice</description><image><title>SRE Engineering Practice</title><url>https://www.sre.wang/share-card-square.jpg</url><link>https://www.sre.wang/share-card-square.jpg</link></image><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 03 Oct 2026 00:34:11 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/auto-rollback/index.xml" rel="self" type="application/rss+xml"/><item><title>Rollback Made It Worse: 5-Layer CI/CD Auto-Rollback Architecture and 4 Production Pitfalls</title><link>https://www.sre.wang/en/posts/cicd-automated-rollback-architecture/</link><pubDate>Sat, 03 Oct 2026 00:34:11 +0800</pubDate><guid>https://www.sre.wang/en/posts/cicd-automated-rollback-architecture/</guid><description>CI/CD auto-rollback is not just adding kubectl rollout undo. This article breaks down a 5-layer rollback architecture covering rollback decisions, health detection, data compatibility, traffic switching, and rollback verification, plus 4 production-level pitfalls and alternative comparisons</description></item></channel></rss>