The DevOps Toolkit Catalogue/

...

/

Initiate the Deployment of the Second Release

Initiate the Deployment of the Second Release

Deploy the releases with fully automated steps and watch the rollouts.

We'll cover the following...

Now that we’re simulating issues, please go back to the first terminal session and initiate the deployment of the second release.

Press + to interact
helm upgrade devops-toolkit helm \
    --namespace devops-toolkit \
    --reuse-values \
    --set image.tag=2.9.9
kubectl argo rollouts \
    --namespace devops-toolkit \
    get rollout devops-toolkit-devops-toolkit \
    --watch

The process should set the weight to 10% right away and pause for the duration of 2m. After that, it should continue the process by executing the second step, which sets the weight to 20%.

Note: The steps are a bit misleading. In the get rollout output (the current one), both setWeight and pause count as steps. However, the startingStep field in the Rollout definition refers only to setWeight as steps.

The process started the analysis as soon as it set the weight to 30%. We can see that through the AnalysisRun in the get rollout output. It should show that one is successful and one is failing. A bit later, it will change both to 2, and then to 3. That means that the analysis of one of the metrics is passing (avg-req-duration), while the other is failing (success-rate).

Soon after the AnalysisRun reached the failureLimit currently set to 3, the process was aborted and the rollback started. The Status changed to Degraded, the ReplicaSet of the new release was ScaledDown, ...