This topic describes how Harness rolls back to the last successful version of your workload in response to failures.
Harness follows standard Kubernetes behavior during rollback. See kubectl rollout undo.
Workload Rollback Only
Rollback rolls back workloads only. If there are other objects or operations executed in your stage, Harness does not roll those back.For details on Harness Kubernetes workloads, see What Can I Deploy in Kubernetes?.
Scaling and Rollback
Each time Harness deploys, the deployment gets new replicas that get scaled up and the old replicas are scaled down.
By default, Kubernetes keeps the last 10 revisions as ReplicaSets.
When Harness performs rollback it identifies which revision number to use (
rollback-to). Harness identifies that last successful ReplicaSet, and selects it to be scaled up.
Rollback and Artifacts
The artifact(s) used for the replicas that are scaled up as part of rollback are simply the artifact(s) from the time that version was deployed.
Blue Green Rollbacks
In the case of Blue Green, the resources are not versioned because a Blue Green deployment uses rapid rollback. Network traffic is simply routed back to the original instances.
You do not need to redeploy previous versions of the service/artifact and the instances that comprised their environment.
Rolling Rollback Step
You can add a Rolling Rollback step to roll back the workloads deployed by the Rolling Deployment step.
Simply add this step where you want to initiate a rollback. Note that this step applies to the deployments of the Rolling Deployment command, and not the Apply Step.