Steps to upgrade
SUSE Observability Self-hosted
Last updated
SUSE Observability Self-hosted
Last updated
To upgrade from StackState 6.0 to SUSE Observability follow the .
This document describes the upgrade procedure for SUSE Observability.
When executing a SUSE Observability upgrade, be aware of the following:
Always read the before upgrading SUSE Observability.
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 SUSE Observability installation, contact SUSE Observability technical support prior to upgrading.
A minor release of SUSE Observability 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 SUSE Observability release or a maintenance release, SUSE Observability 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
A major release of SUSE Observability 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 SUSE Observability it's recommended to back up your configuration and topology data:
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
.
Once SUSE Observability has been upgraded and started, verify that the new installation of SUSE Observability is reachable and that the application is running.
If you upgrade to a new major SUSE Observability release, SUSE Observability and the installed StackPacks may be incompatible with the current installation. For details, check the .
Optional:
Optional:
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.
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.
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.