Merge pull request #30211 from bergerhoffer/GitHub-27639

GitHub-27639: Switching blue and green references

Author: bergerhoffer

applications/deployments/route-based-deployment-strategies.adoc

@@ -18,7 +18,7 @@ for more on the basic strategy types.
 ====
 ////
 
-The most common route-based strategy is to use a _blue-green deployment_. The new version (the blue version) is brought up for testing and evaluation, while the users still use the stable version (the green version). When ready, the users are switched to the blue version. If a problem arises, you can switch back to the green version.
+The most common route-based strategy is to use a _blue-green deployment_. The new version (the green version) is brought up for testing and evaluation, while the users still use the stable version (the blue version). When ready, the users are switched to the green version. If a problem arises, you can switch back to the blue version.
 
 A common alternative strategy is to use _A/B versions_ that are both active at the same time and some users use one version, and some users use the other version. This can be used for experimenting with user interface changes and other features to get user feedback. It can also be used to verify proper operation in a production context where problems impact a limited number of users.
 

modules/deployments-blue-green.adoc

@@ -5,7 +5,7 @@
 [id="deployments-blue-green_{context}"]
 = Blue-green deployments
 
-Blue-green deployments involve running two versions of an application at the same time and moving traffic from the in-production version (the green version) to the newer version (the blue version). You can use a rolling strategy or switch services in a route.
+Blue-green deployments involve running two versions of an application at the same time and moving traffic from the in-production version (the blue version) to the newer version (the green version). You can use a rolling strategy or switch services in a route.
 
 Because many applications depend on persistent data, you must have an application that supports _N-1 compatibility_, which means it shares data and implements live migration between the database, store, or disk by creating two copies of the data layer.
 
@@ -21,41 +21,41 @@ Blue-green deployments use two `DeploymentConfig` objects. Both are running, and
 Routes are intended for web (HTTP and HTTPS) traffic, so this technique is best suited for web applications.
 ====
 
-You can create a new route to the new version and test it. When ready, change the service in the production route to point to the new service and the new (blue) version is live.
+You can create a new route to the new version and test it. When ready, change the service in the production route to point to the new service and the new (green) version is live.
 
-If necessary, you can roll back to the older (green) version by switching the service back to the previous version.
+If necessary, you can roll back to the older (blue) version by switching the service back to the previous version.
 
 .Procedure
 
 . Create two independent application components.
-.. Create a copy of the example application running the `v1` image under the `example-green` service:
+.. Create a copy of the example application running the `v1` image under the `example-blue` service:
 +
 [source,terminal]
 ----
-$ oc new-app openshift/deployment-example:v1 --name=example-green
+$ oc new-app openshift/deployment-example:v1 --name=example-blue
 ----
 +
-.. Create a second copy that uses the `v2` image under the `example-blue` service:
+.. Create a second copy that uses the `v2` image under the `example-green` service:
 +
 [source,terminal]
 ----
-$ oc new-app openshift/deployment-example:v2 --name=example-blue
+$ oc new-app openshift/deployment-example:v2 --name=example-green
 ----
 
 . Create a route that points to the old service:
 +
 [source,terminal]
 ----
-$ oc expose svc/example-green --name=bluegreen-example
+$ oc expose svc/example-blue --name=bluegreen-example
 ----
 
-. Browse to the application at `example-green.<project>.<router_domain>` to verify you see the `v1` image.
+. Browse to the application at `example-blue.<project>.<router_domain>` to verify you see the `v1` image.
 
-. Edit the route and change the service name to `example-blue`:
+. Edit the route and change the service name to `example-green`:
 +
 [source,terminal]
 ----
-$ oc patch route/bluegreen-example -p '{"spec":{"to":{"name":"example-blue"}}}'
+$ oc patch route/bluegreen-example -p '{"spec":{"to":{"name":"example-green"}}}'
 ----
 
 . To verify that the route has changed, refresh the browser until you see the `v2` image.