Fusion 5 Upgrade from 5.4.x
This article includes instructions for upgrading Fusion from one version to another. In some cases, the instructions do not vary. Other upgrades require special instructions. Start by checking upgrade details for your target version before continuing to the General upgrade process.
Remember, upgrade instructions may vary between deployment types too. Review Upgrades by deployment type for details.
Whenever you upgrade Fusion, you must also update your remote connectors, if you are running any. Configure Remote V2 Connectors provides complete instructions for remote connector setup. You can download the latest files at V2 Connectors Downloads.
Upgrades from 5.4.x
to 5.4.y
Upgrade from 5.4.x to 5.4.y using the General upgrade process.
to 5.5.y
Upgrading from 5.4.x to 5.5.y involves using the General upgrade process.
General upgrade process
Fusion natively supports deployments on various Kubernetes platforms, including AKS, EKS, and GKE. You can also deploy on a different Kubernetes platform of your choice.
Fusion includes an upgrade script for AKS, EKS, and GKE. This script is not generated for other Kubernetes deployments. In this case, see Other Kubernetes deployment upgrades.
Upgrades differ from platform to platform. See below for more information about upgrading on your platform of choice.
Whenever you upgrade Fusion, you must also update your remote connectors, if you are running any. Configure Remote V2 Connectors provides complete instructions for remote connector setup. You can download the latest files at V2 Connectors Downloads.
Natively supported deployment upgrades
Deployment type | Platform |
---|---|
Azure Kubernetes Service (AKS) |
|
Amazon Elastic Kubernetes Service (EKS) |
|
Google Kubernetes Engine (GKE) |
|
Fusion includes upgrade scripts for natively supported deployment types. To upgrade:
-
Open the
<platform>_<cluster>_<release>_upgrade_fusion.sh
upgrade script file for editing. -
Update the
CHART_VERSION
to your target Fusion version, and save your changes. -
Run the
<platform>_<cluster>_<release>_upgrade_fusion.sh
script. The<release>
value is the same as your namespace, unless you overrode the default value using the-r
option.
After running the upgrade, use kubectl get pods
to see the changes applied to your cluster. It may take several minutes to perform the upgrade, as new Docker images are pulled from DockerHub. To see the versions of running pods, do:
kubectl get po -o jsonpath='{..image}' | tr -s '[[:space:]]' '\n' | sort | uniq