From 4b7da155de0daf818c7db58e26fc4fd57549bf86 Mon Sep 17 00:00:00 2001
From: Kyle McLaren <mclaren@fly.io>
Date: Wed, 4 Sep 2024 14:44:14 +0200
Subject: [PATCH] bluegreen strategy disclaimer

---
 blueprints/sticky-sessions.html.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/blueprints/sticky-sessions.html.md b/blueprints/sticky-sessions.html.md
index 93479756da..f728679d82 100644
--- a/blueprints/sticky-sessions.html.md
+++ b/blueprints/sticky-sessions.html.md
@@ -6,6 +6,10 @@ author: rubys
 date: 2024-07-17
 ---
 
+<div class="important">
+The methods described in this Blueprint won't work with a [Bluegreen deployment strategy](https://fly.io/docs/launch/deploy/#deployment-strategy) because all the Machines in your app are replaced—the old Machines are destroyed and their IDs are no longer relevant.
+</div>
+
 In a number of scenarios, it is important to ensure that certain requests are
 routed to a specific Machine.  This frequently is expressed in the form of
 wanting an entire user's session to be processed by the same Machine.