Check image

OpenShiftDemos · Oct 16, 2023 · 45b2c04 · 45b2c04
1 parent bcf5ffe
commit 45b2c04
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 0 deletions.
diff --git a/documentation/modules/ROOT/assets/images/overview-blue-green.png b/documentation/modules/ROOT/assets/images/overview-blue-green.png
diff --git a/documentation/modules/ROOT/nav.adoc b/documentation/modules/ROOT/nav.adoc
@@ -8,4 +8,5 @@
 ** xref:02-workshop-overview.adoc#deploy-application[Deploy Application]
 
 * xref:03-bluegreen-rollout.adoc[3. Blue-Green Rollout]
+** xref:03-bluegreen-rollout.adoc#deploy-blue-green-overview[Blue-Green Overview]
 ** xref:03-bluegreen-rollout.adoc#deploy-blue-green-rollout[Deploy Blue-Green Rollout]
diff --git a/documentation/modules/ROOT/pages/03-bluegreen-rollout.adoc b/documentation/modules/ROOT/pages/03-bluegreen-rollout.adoc
@@ -1,5 +1,18 @@
 = Blue-Green Rollout
 include::_attributes.adoc[]
 
+[#blue-green-overview]
+== Blue-Green Overview
+
+In a blue-green deployment we deploy a new version of the application in a separate stack from the current version with
+the two versions running in parallel for a period of time. This enables testing on the new version while users continue
+to access the current version of the application until a cut-over of traffic happens. The diagram below shows this process
+over time.
+
+image::overview-blue-green.png[]
+
+
+
+
 [#deploy-blue-green-rollout]
 == Deploy Blue-Green Rollout