<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blue-Green Deployment on 📋 JayJay's DevOps Diaries ..</title><link>http://halfknown.co.uk/tags/blue-green-deployment/</link><description>Recent content in Blue-Green Deployment on 📋 JayJay's DevOps Diaries ..</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 07 Jun 2026 08:58:59 +0000</lastBuildDate><atom:link href="http://halfknown.co.uk/tags/blue-green-deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Linkerd + Deployment Strategy - PART 2 {Blue-Green}</title><link>http://halfknown.co.uk/pages/linkerd-blue-green/</link><pubDate>Sun, 24 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/pages/linkerd-blue-green/</guid><description>&lt;h1 id="introcktion">Introcktion&lt;/h1>
&lt;p>This article is the second in a series demonstrating different &lt;strong>deployment strategies&lt;/strong> for modern cloud‑native applications. Following our previous exploration, this time we will focus specifically on &lt;strong>Blue‑Green Deployment&lt;/strong>, and show how to implement it effectively using &lt;strong>Linkerd as the service mesh&lt;/strong>.&lt;/p>
&lt;p>This is a direct continuation of the first article:&lt;/p>
&lt;p>&lt;strong>
&lt;a href="http://halfknown.co.uk/pages/servicemesh-linkered/">Linkerd + Deployment Strategy – PART 1 {Canary}&lt;/a>&lt;/strong>&lt;/p>
&lt;p>The whole series was originally inspired by a lively discussion among fellow DevOps engineers in a WhatsApp group, where we compared and debated the best approaches for safe, reliable software releases.&lt;/p></description></item></channel></rss>