Steps to upgrade
StackState for Kubernetes troubleshooting Self-hosted
Overview
This document describes the upgrade procedure for StackState.
Before you upgrade
When executing a StackState upgrade, be aware of the following:
Always read the version-specific upgrade notes before upgrading StackState.
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 minor upgrade consists of the following steps:
Check if any installed StackPacks require an upgrade
Major StackState release
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 upgrade to a new major StackState release, StackState and 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:
Optional: Uninstall StackPacks
Optional: Install StackPacks
Walkthrough of an upgrade
Create a backup
Before upgrading StackState it's recommended to back up your configuration and topology data:
Note that it won't be possible to restore the backup on the upgraded version of StackState. The StackState backup can only be restored in the StackState version before the upgrade.
Upgrade StackState
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.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.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.
Verify the new installation
Once StackState has been upgraded and started, verify that the new installation of StackState is reachable and that the application is running.
See also
Last updated
