Use the appropriate upgrade bundle to upgrade Bare Metal Orchestrator from one version to another.
Upgrade nomenclature:
- Major upgrade—For example, upgrading from release 2.0 to release 3.0.
- Minor upgrade—For example, upgrading from release 2.0 to 2.1.
- Patch upgrade—For example, upgrading from release 2.0.0 to 2.0.1.
The following table lists the available upgrade paths for the latest Bare Metal Orchestrator release version.
Bare Metal Orchestrator bundle and patch upgrades | Description |
Upgrade from release 2.0.x to release 2.1.x | Upgrade all components in Bare Metal Orchestrator from release 2.0.x to release 2.1.x. During the upgrade, existing GlusterFS data automatically migrates to the internal Bare Metal Orchestrator storage facility that is replacing GlusterFS. Note: The upgrade procedure from release 2.0.x to release 2.1.x is supported for HA deployments only. For information about upgrading from release 2.0.x to release 2.1.x, see the release 2.1 version of the Bare Metal Orchestrator Installation Guide. |
Upgrade from release 2.1.x to release 2.2 | Upgrade the platform, sites, and RKE2 nodes in Bare Metal Orchestrator from release 2.1.x to release 2.2. For more information about upgrading Bare Metal Orchestrator from release 2.1.x to 2.2, see Upgrade Bare Metal Orchestrator. |