Overview
Aviatrix encourages you to keep your platform Controller and gateways up to date to ensure you are operating the most secure and highest performing versions available. To facilitate less disruptive upgrades and reduce maintenance windows Aviatrix provides a rolling selective upgrade process. You can choose to upgrade all Aviatrix gateways in all regions simultaneously or select specific gateways and regions to upgrade in logical groups conforming to your network update policies and maintenance windows.About Aviatrix Upgrade
There are two types of upgrades for the Aviatrix Platform and gateways:- Software Upgrade (Controller and Gateway): Update the Aviatrix software without creating new instances. This software upgrades replace the relevant Aviatrix Controller and gateway packages, configuration files, and binaries without disrupting network traffic or replacing the gateways. The software upgrade causes minimal disruption to network traffic.
- Controller Image Upgrade: Updates the base image of the controller, which is needed for operating system or kernel upgrades and may include an Aviatrix software upgrade. This results in minimal disruption to network traffic.
- Gateway Image Upgrade: Updates the base image of the gateway, potentially causing brief traffic disruptions. To minimize impact, deploying gateways with high availability (HA) is recommended, and upgrades should be performed on one gateway at a time within the HA set. Gateway image upgrades are usually required after a Controller Image Upgrade to ensure that the Aviatrix Platform and gateways are operating with the same base software version.
- Security Patches Security patches are released when security updates to underlying software components become available. Review the patch release notes for more details.
- Software Patches Software patches are released to address compatibility issues when they arise. You should apply the patches to the Aviatrix system when they become available if you are using any applications or configurations affected by the patch. Review the patch release notes for more details.
About Release Numbers
Aviatrix release numbers follow the Major.Minor.Build format. For example, the release number 7.1.100 indicates:- 7 is the major release number.
- 1 is the minor release number.
- 100 is the build number.
- Major Includes new features and updates that affect the platform infrastructure and user interfaces.
- Minor Includes modified and new small features and updates that may affect the platform infrastructure and user interfaces.
- Build Corrected issues and feature enhancements.
Upgrade Options
When you initiate an upgrade, Aviatrix automatically presents the most recently published build for the selected major or minor release version.Upgrading Minor Releases of Controller and Gateways
When upgrading from one minor version of a major release to another, it is necessary to follow a sequential upgrade process and cannot skip over intermediate minor release versions. Each minor release must be upgraded sequentially. For instance, when upgrading from 6.5.current to 6.8.latest, the intermediate releases 6.6.latest and 6.7.latest must be upgraded first. Valid upgrade paths to a new minor release are determined by the current build (the one currently running) and the latest build available on the Aviatrix server.Upgrading Major Releases of Controller and Gateways
When upgrading from one major release to another, it is required to perform a sequential upgrade and not skip over intermediate major release versions. Each major release must be upgraded in sequence. You also need to go through all the minor releases within each major release before moving on to the next major release. For example, if you are currently on version 6.6.current and want to upgrade to version 8.0, you need to:- Upgrade from 6.6 to the latest minor release in the 6.x series (e.g., 6.6.current to 6.6.latest, then to 6.7.latest, then 6.7.latest to 6.8.latest, and so on) until you reach the latest minor release in the 6.x series.
- Once you have upgraded through all the minor releases in the 6.x series, you can then move on to the major release 7.0.
- From 7.0, continue upgrading through all the minor releases in the 7.x series until you reach the latest minor release in the 7.x series.
- Upgrade from the latest minor release in the 7.x series to version 8.0.