Add cleanup steps to bluegreen module

OpenShiftDemos · Oct 19, 2023 · d2dc199 · d2dc199
1 parent 3297650
commit d2dc199
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 0 deletions.
diff --git a/documentation/modules/ROOT/nav.adoc b/documentation/modules/ROOT/nav.adoc
@@ -13,6 +13,7 @@
 ** xref:03-bluegreen-rollout.adoc#argo-rollouts-dashboard[Argo Rollouts Dashboard]
 ** xref:03-bluegreen-rollout.adoc#promote-image[Promote Image]
 ** xref:03-bluegreen-rollout.adoc#enable-auto-promotion[Enable Auto-Promotion]
+** xref:03-bluegreen-rollout.adoc#cleanup[Clean-up]
 
 * xref:04-analysis.adoc[4. Analysis]
 ** xref:04-analysis.adoc#analysis-overview[Analysis Overview]

diff --git a/documentation/modules/ROOT/pages/03-bluegreen-rollout.adoc b/documentation/modules/ROOT/pages/03-bluegreen-rollout.adoc
@@ -342,3 +342,22 @@ note that there is a new revision using the Yellow image associated with the Act
 While not requiring manual intervention is great, it would be wonderful if there was a way to perform automated testing to ensure
 the validity of the new reviewion before Rollouts makes it available to users. Fortunately Rollouts can do this with the Analysis feature
 which will be covered that in the next module.
+
+[#cleanup]
+== Clean-up
+
+Prior to moving on to the next module we need to perform some clean-up activites. First let's reset the Development environment back to blue:
+
+[.console-input]
+[source,bash,subs="attributes+,+macros"]
+----
+oc apply -k ./deploy/base -n user%USERNUM%-dev
+----
+
+Next we will delete the Rollout in the `user%USERNUM%-prod` so we can start with a fresh version.
+
+[.console-input]
+[source,bash,subs="attributes+,+macros"]
+----
+oc delete -k ./bluegreen/base -n user%USERNUM%-prod
+----