Upgrade Cloudbreak to the latest version

	Note
	As of December 31, 2021, Cloudbreak reached end of support. For more information, see Support lifecycle policy. Cloudera recommends that you migrate your workloads to CDP Public Cloud.

For correct upgrade steps, always refer to the documentation published for the Cloudbreak version that you are upgrading to. For example, if you are currently using Cloudbreak 2.7.0 and you would like to upgrade to 2.9.0, refer to 2.9.0 documentation.

These steps only allow you to upgrade to the latest general availability release. They cannot be used for upgrading to a technical preview release.

Prerequisites

You must back up Cloudbreak databases before upgrading. For instructions, refer to Back up Cloudbreak database.

Steps

1. Access the VM where Cloudbreak is running via SSH.
2. If you launched Cloudbreak from a quickstart template, run the following to obtain root access:

   sudo su

   If you installed Cloudbreak manually, this step is not required.
3. Navigate to the Cloudbreak deployment directory. By default, this is /var/lib/cloudbreak-deployment/:

   cd /var/lib/cloudbreak-deployment/

4. To ensure that the cbd is running, restart Cloudbreak by using cbd restart or if the deployment is stopped start it by using cbd start
5. Update Cloudbreak deployer:

   cbd update

   cbd update always updates Cloudbreak to the latest available general availability version.

6. Stop all of the running Cloudbreak components:

   cbd kill

7. Update the docker-compose.yml file with new Docker containers needed for the cbd:

   cbd regenerate

8. If there are no other Cloudbreak instances that still use old Cloudbreak versions, remove the obsolete containers:

   cbd util cleanup

9. Check the health and version of the updated cbd:

   cbd doctor

10. Start the new version of the cbd:

    cbd start

    Cloudbreak needs to download updated docker images for the new version, so this step may take a while.