Cleanup

OpenShiftDemos · Oct 23, 2023 · 98f38eb · 98f38eb
1 parent 031a0ff
commit 98f38eb
Show file tree

Hide file tree

Showing 5 changed files with 1 addition and 13 deletions.
diff --git a/documentation/modules/ROOT/nav.adoc b/documentation/modules/ROOT/nav.adoc
@@ -8,21 +8,18 @@
 ** 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]
 ** 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]
 ** xref:04-analysis.adoc#analysis-deployment[Analysis Deployment]
 ** xref:04-analysis.adoc#analysis-promotion[Promotion with Analysis]
 ** xref:04-analysis.adoc#cleanup[Clean-up]
 
 * xref:05-canary-rollout.adoc[5. Canary Rollout]
-** xref:05-canary-rollout.adoc#canary-overview[Canary Overview]
 ** xref:05-canary-rollout.adoc#deploy-canary-rollout[Deploy Canary Rollout]
 ** xref:05-canary-rollout.adoc#promote-image[promote Image]
 ** xref:05-canary-rollout.adoc#inline-analysis[Inline Analysis]

diff --git a/documentation/modules/ROOT/pages/03-bluegreen-rollout.adoc b/documentation/modules/ROOT/pages/03-bluegreen-rollout.adoc
@@ -1,9 +1,6 @@
 = 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.

diff --git a/documentation/modules/ROOT/pages/04-analysis.adoc b/documentation/modules/ROOT/pages/04-analysis.adoc
@@ -1,9 +1,6 @@
 = Analysis
 include::_attributes.adoc[]
 
-[#analysis-overview]
-== Analysis Overview
-
 When performing upgrades of services there is a need to test the new version
 that is being deployed to ensure functionality is not being negatively impacted. The
 link:https://argo-rollouts.readthedocs.io/en/stable/features/analysis[Analysis,window='_blank'] feature

diff --git a/documentation/modules/ROOT/pages/05-canary-rollout.adoc b/documentation/modules/ROOT/pages/05-canary-rollout.adoc
@@ -1,9 +1,6 @@
 = Canary
 include::_attributes.adoc[]
 
-[#canary-overview]
-== Canary Overview
-
 link:https://argo-rollouts.readthedocs.io/en/stable/features/canary/[Canary, window='_blank'] can be thought of as an advanced version of blue-green where instead of an abrupt cut-over
 of live traffic between a current and new revision instead traffic is gradually increased to the new
 version in increments, or steps. Like the proverbial link:https://en.wiktionary.org/wiki/canary_in_a_coal_mine[canary in the coal mine,window="_blank"],

diff --git a/documentation/modules/ROOT/pages/06-conclusion.adoc b/documentation/modules/ROOT/pages/06-conclusion.adoc
@@ -9,7 +9,7 @@ Analysis to perform automated testing of the Rollout.
 
 To learn more about Argo Rollouts, please feel free to checkout this resources:
 
-* link:https://argo-rollouts.readthedocs.io/en/stable/[Argo Rollout documentation, window='_blank']
+* link:https://argo-rollouts.readthedocs.io/en/stable/[Argo Rollouts documentation, window='_blank']
 
 * link:https://www.redhat.com/architect/blue-green-canary-argo-rollouts[How to do blue/green and canary deployments with Argo Rollouts,window='_blank']