Steps to upgrade
StackState Self-hosted v5.1.x
Last updated
StackState v5.1
StackState Self-hosted v5.1.x
Last updated
This document describes the upgrade procedure for StackState.
For instructions on how to upgrade StackPacks, see .
When executing a StackState upgrade, be aware of the following:
Always read the before upgrading StackState.
When upgrading a StackPack, any changes you have made to configuration items from that StackPack will be overwritten. See for more information.
If there are hotfixes installed in your StackState installation, contact StackState technical support prior to upgrading.
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.
A major upgrade consists of the following steps:
Before upgrading StackState it's recommended to back up your configuration and topology data.
To create a backup on Kubernetes, see:
Manually created topology backup
When uninstalling StackPacks, the version of StackState prior to the upgrade must be used since this version can contain different installation logic from the new StackPack version.
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.
Depending on your platform, use one of the following commands to upgrade:
Fedora, RedHat, CentOS:
using RPM: rpm -U <stackstate>.rpm
using yum: yum localinstall <stackstate>.rpm
Debian, Ubuntu:
using dpkg: dpkg -i <stackstate>.deb
using apt: apt-get upgrade <stackstate>.deb
Once StackState has been upgraded and started, verify that the new installation of StackState is reachable and that the application is running.
If you upgrade to a new major StackState release, StackState and the installed StackPacks may be incompatible with the current installation. For details, check the .
Optional:
Optional:
See for more information.
Check the for specific changes that need to be made for the new StackState version you will upgrade to.
Download the upgrade file from .
Check the for all changes between your current version and the version that you will upgrade to. If there have been changes made to configuration items specified in your values.yaml file, the file should be updated accordingly.
To upgrade, use the same helm command as for the . The new helm chart will pull newer versions of Docker images and handle the upgrade.
Check the for all changes between your current version and the version that you will upgrade to. If there have been changes made to configuration items specified in your values.yaml file, the file should be updated accordingly.
file.
To upgrade, use the same helm command as for the . The new helm chart will pull newer versions of Docker images and handle the upgrade.
See for more information.