This document describes the upgrade procedure for StackState.
For instructions on how to upgrade StackPacks, see the StackPacks documentation.
When executing a StackState upgrade, please be aware of the following:
A minor release of StackState is indicated by a change in the second digit of the version number, for example 4.1.0. Maintenance releases are identified by a change in the third digit of the version number, for example 4.1.1.
If you are upgrading to a new minor StackState release or a maintenance release, StackState itself and the StackPacks will be compatible with the current installation.
A minor upgrade consists of the following steps:
A major release of StackState is indicated by a change in the first digit of the version number, for example 4.0.0.
If you are upgrading to a new major StackState release, StackState and/or the installed StackPacks may be incompatible with the current installation. For details, check the version-specific upgrade notes.
A major upgrade consists of the following steps:
Before upgrading StackState it is recommended to backup your configuration and topology data.
See Uninstalling StackPacks for more information.
Instructions to upgrade a StackState Kubernetes or Linux setup can be found below.Be sure to check the release notes and any optional upgrade notes before running the upgrade.
Get the latest helm chart by running
helm repo update.
To upgrade, use the same command as for the first time Kubernetes installation. The new helm chart will pull newer versions of Docker images and handle the upgrade.
Download the upgrade file from https://download.stackstate.com.
Depending on your platform, use one of the following commands to upgrade:
Fedora, RedHat, CentOS:
rpm -U <stackstate>.rpm
yum localinstall <stackstate>.rpm
dpkg -i <stackstate>.deb
apt-get upgrade <stackstate>.deb
See Installing StackPacks for more information.
Once StackState has been upgraded and started, verify that the new installation of StackState is reachable and that the application is running.