Comment on page
Steps to upgrade
StackState Self-hosted v5.0.x
This page describes StackState version 5.0.
This document describes the upgrade procedure for StackState.
When executing a StackState upgrade, be aware of the following:
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.
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:
- 1.
- 2.
- 4.
Before upgrading StackState it is recommended to backup your configuration and topology data.
Kubernetes
Linux
To create a backup on Kubernetes, see:
To create a backup on Linux, see:
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.
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.
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.
Linux
Kubernetes
OpenShift
- 1.
- 2.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
- 1.Get the latest helm chart by running
helm repo update. - 2.Check the version specific upgrade notes 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.yamlfile, the file should be updated accordingly. - 3.To upgrade, use the same helm command as for the first time Kubernetes installation. The new helm chart will pull newer versions of Docker images and handle the upgrade.
- 1.Get the latest helm chart by running
helm repo update. - 2.Check the version specific upgrade notes 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.yamlfile, the file should be updated accordingly. - 3.
- 4.To upgrade, use the same helm command as for the first time OpenShift installation. The new helm chart will pull newer versions of Docker images and handle the upgrade.
Once StackState has been upgraded and started, verify that the new installation of StackState is reachable and that the application is running.
Last modified 1yr ago