When upgrading a StackPack, any changes you have made to configuration items from that StackPack will be overwritten. See Configuration Locking for more information.
If there are hotfixes installed in your StackState installation, contact StackState technical support prior to upgrading.
Steps to upgrade
Minor or maintenance StackState release
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 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.
Note that it will not be possible to restore the backup on the upgraded version of StackState. The StackState backup can only be restored in the StackState and StackPack versions prior to the upgrade.
StackPacks must be uninstalled using the version of StackState prior to the upgrade since this version can contain different installation logic from the new StackPack version.
Upgrade StackState
Remember to check the version specific upgrade notes for specific changes that need to be made for the new StackState version you will upgrade to.
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.
Kubernetes
Linux
1.
Get the latest helm chart by running helm repo update.
2.
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.