Corda 5.2 Now Available

Corda 4.12 Now Available

Rolling Back

To roll back the Corda 5.1 to Corda 5.2 upgrade process, restore the database backups and restart the Corda 5.1 workers.

You can no longer roll back an upgrade after:

Kafka topics or ACLs are deleted. R3 recommends that you do not delete old topics or ACLs until the upgrade to Corda 5.2 is complete.
Corda 5.2 workers are launched and marked as READY in Kubernetes.

To restart the Corda 5.0 workers, you can do one of the following:

Reverse the commands in Scale Down the Running Corda Worker Instances that scaled the workers to zero replicas.

Issue a Helm upgrade command that resets the values you installed Corda 5.1 with, which includes replica counts. For example:

helm upgrade corda -n <corda_namespace> \
oci://corda-os-docker.software.r3.com/helm-charts/release-5.1.0.0/corda \
--version "5.1.0" \
--values values.yaml \
--wait