<?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>Preview Environments on rtnpro</title><link>https://rtnpro.com/tags/Preview-Environments/</link><description>Recent content in Preview Environments on rtnpro</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 26 Aug 2026 00:45:00 +0530</lastBuildDate><atom:link href="https://rtnpro.com/tags/Preview-Environments/index.xml" rel="self" type="application/rss+xml"/><item><title>Preview Environments That Actually Promote to Prod</title><link>https://rtnpro.com/post/2026-08-26-preview-environments-promote-to-prod/</link><pubDate>Wed, 26 Aug 2026 00:45:00 +0530</pubDate><guid>https://rtnpro.com/post/2026-08-26-preview-environments-promote-to-prod/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Last week&amp;rsquo;s post closed with a promise that was really four promises: preview environments per change, release trains where stable and canary share a namespace, weighted traffic splitting on Gateway API &lt;code&gt;HTTPRoute&lt;/code&gt;s, and promotion gates between all of it. Honesty being the house rule of this series: two of those four are running in anger, and two are still designs. This post is about the real two — ephemeral previews and promotion — and ends with a straight account of the other two, because I&amp;rsquo;d rather correct myself than let a closing paragraph quietly become marketing.&lt;/p&gt;</description></item></channel></rss>