Merge pull request #30822 from sagidlow/ISSUE-29111

ISSUE-29111 Updated code to include missing label

Author: jeana-redhat

modules/deployments-ab-testing-lb.adoc

@@ -205,7 +205,8 @@ Not all routers may support multiple or weighted backends.
 +
 [source,terminal]
 ----
-$ oc new-app openshift/deployment-example --name=ab-example-a
+$ oc new-app openshift/deployment-example --name=ab-example-a --as-deployment-config=true --labels=ab-example=true --env=SUBTITLE\=shardA
+$ oc delete svc/ab-example-a
 ----
 +
 The application is deployed and a service is created. This is the first shard.
@@ -214,18 +215,20 @@ The application is deployed and a service is created. This is the first shard.
 +
 [source,terminal]
 ----
-$ oc expose svc/ab-example-a --name=ab-example
+$ oc expose deploymentconfig ab-example-a --name=ab-example --selector=ab-example\=true
+$ oc expose service ab-example
 ----
 
-. Browse to the application at `ab-example-<project>.<router_domain>` to verify you see the `v1` image.
+. Browse to the application at `ab-example-<project_name>.<router_domain>` to verify you see the `v1` image.
 
 . Create a second shard based on the same source image and label as the first shard, but with a different tagged version and unique environment variables:
 +
 [source,terminal]
 ----
 $ oc new-app openshift/deployment-example:v2 \
     --name=ab-example-b --labels=ab-example=true \
-    SUBTITLE="shard B" COLOR="red"
+    SUBTITLE="shard B" COLOR="red" --as-deployment-config=true
+$ oc delete svc/ab-example-b
 ----
 
 . At this point, both sets of pods are being served under the route. However, because both browsers (by leaving a connection open) and the router (by default, through a cookie) attempt to preserve your connection to a back-end server, you might not see both shards being returned to you.