Upgrade on a Kubernetes environment
The Axiomatics Services Manager (ASM) upgrading process can only be performed between two consecutive minor versions, meaning that you must be running version 7.4 in order to upgrade to version 7.5. Patching, however, is possible in between any two 7.5 patches.
Upgrading or patching ASM will cause downtime for the application and consequently a temporary loss of service. As a result, the upgrade should be planned accordingly.
For local installations only, it is crucial to backup your system before proceeding with an ASM upgrade due to a major PostgreSQL update. Failing to do so will lead to data loss and and render the system inoperable.
The instructions below apply to both local and cloud environments when upgrading or patching ASM.
For cloud installations only, if you are upgrading ASM, update PostgreSQL to version 15.4 following the instructions in the AWS documentation.
Download the ASM 7.5 distribution.
aws s3api get-object --bucket axiomatics-customer-artifacts --key releases/com/axiomatics/axiomatics-services-manager/axiomatics-services-manager/7.5.0-0/axiomatics-services-manager-7.5.0-0.zip axiomatics-services-manager-7.5.0-0.zipExtract the contents of the downloaded ZIP file.
tipOptionally, if you want to build your own images, navigate to the
docker/folder and build the images following the instructions provided here. This also applies if you are using custom Attribute Connectors, including the older http-pip and/or parser-pip.Navigate to the
kubernetesfolder and add theaxiomatics_ASM.licenselicense file.Open the
kubernetes/asmcharts/values.yamlfile and set the appropriate configuration values that correspond to the original installation.tipAlternatively, you can skip this step and use the
--setflag in the command below to pass directly the appropriate configuration values.Upgrade the Helm charts.
helm upgrade -n axiomatics-asm asm -f asmcharts/values.yaml asmchartsFor local installations only, if you are upgrading ASM, restore your backed up data.