<?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>渐进式交付 on SRE工程实践</title><link>https://www.sre.wang/tags/%E6%B8%90%E8%BF%9B%E5%BC%8F%E4%BA%A4%E4%BB%98/</link><description>Recent content in 渐进式交付 on SRE工程实践</description><image><title>SRE工程实践</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>zh-cn</language><lastBuildDate>Sat, 17 Oct 2026 00:05:38 +0800</lastBuildDate><atom:link href="https://www.sre.wang/tags/%E6%B8%90%E8%BF%9B%E5%BC%8F%E4%BA%A4%E4%BB%98/index.xml" rel="self" type="application/rss+xml"/><item><title>切流量切到一半数据库连接池炸了：蓝绿与金丝雀发布的 6 个生产级决策与流量治理实录</title><link>https://www.sre.wang/posts/cicd-blue-green-canary-deployment/</link><pubDate>Sat, 17 Oct 2026 00:05:38 +0800</pubDate><guid>https://www.sre.wang/posts/cicd-blue-green-canary-deployment/</guid><description>蓝绿部署和金丝雀发布不是切个流量那么简单。本文从 K8s 原生 Deployment 的局限讲起，拆解 Argo Rollouts + Istio 的渐进式交付架构，覆盖数据库迁移兼容、流量镜像验证、自动回滚门禁等 6 个生产级决策，附完整可复制的 YAML 配置和性能对比数据。</description></item><item><title>回滚了却比不回滚还惨：CI/CD 自动回滚体系的 5 层架构与 4 个生产级踩坑</title><link>https://www.sre.wang/posts/cicd-automated-rollback-architecture/</link><pubDate>Sat, 03 Oct 2026 00:04:52 +0800</pubDate><guid>https://www.sre.wang/posts/cicd-automated-rollback-architecture/</guid><description>CI/CD自动回滚不是加一个kubectl rollout undo的事。本文从回滚决策、健康判定、数据兼容、流量切换到回滚验证，拆解5层回滚架构，给出4个生产级踩坑实录和替代方案对比</description></item></channel></rss>