diff --git a/argo-rollouts-workshop/main/05-canary-rollout.html b/argo-rollouts-workshop/main/05-canary-rollout.html index bdfac59..716c8b1 100644 --- a/argo-rollouts-workshop/main/05-canary-rollout.html +++ b/argo-rollouts-workshop/main/05-canary-rollout.html @@ -578,6 +578,70 @@

Promote Image argo rollouts dashboard canary pause +
+

Now let’s see the behavior of the routes, first if you check the stable you will see +the blue version of the application:

+
+
+
+
oc get route -n user%USERNUM%-prod stable -o jsonpath='{"https://"}{.spec.host}{"\n"}'
+
+
+
+
+rollouts demo app blue +
+
+
+

Next if we check the canary version of the application we should see the green version +of the application.

+
+
+
+
oc get route -n user%USERNUM%-prod canary -o jsonpath='{"https://"}{.spec.host}{"\n"}'
+
+
+
+
+rollouts demo app green +
+
+
+

Finally if we check the version of the application being delivered by the all route +which includes all pods there will be approximately 20% green squares versus 80% +blue squares:

+
+
+
+
oc get route -n user%USERNUM%-prod all -o jsonpath='{"https://"}{.spec.host}{"\n"}'
+
+
+
+
+rollouts demo app canary blue green +
+
+
+

To promote the rollout, you can either promote it from the dashboard using the Promote +button or you can promote it using the following command:

+
+
+
+
oc argo rollouts promote rollouts-demo -n user%USERNUM%-prod
+
+
+
+

Observe the dashboard once it has been promoted, the dashboard will show the progression +of the steps by highlight each step as it is being executed.

+
+ + +
+

Inline Analysis

+
+
+

In the last section there was a pause step that provided an opportunity

+