Upgrade Allure Testops via Kubernetes

Examples do not contain the commands for the creation of a separate name space for Allure Testops, please consider creating dedicated name space for Allure Testops and use the reference to the created name space in all commands.

This guide describes the common upgrade procedure for an Allure Testops instance that has been installed via Kubernetes.

All the instructions in this guide assume that Allure Testops is installed in the default namespace of the Kubernetes cluster. If it is installed in a different namespace, add the --namespace=... option to the commands.

Before you begin, make sure to read the release notes for the Allure Testops version you are upgrading to. In case you are skipping one or more versions, read the release notes for the skipped versions, too.

The release notes may contain crucial information on how to adapt your configuration files or migrate your data to the new version of Allure Testops.

Open a terminal application.
Refresh the repository data.
```
helm repo update
```
Navigate to the directory containing the values.yaml file, for example:
```
cd ~/allure-testops
```
Perform the upgrade:
```
helm upgrade allure-testops qameta/allure-testops --values values.yaml --set readinessProbe.enabled=false --set livenessProbe.enabled=false
```
At this point, you will need to wait for two time-consuming operation to finish:
1. Before any services can start, Kubernetes needs to download the necessary images from the internet.
2. During the startup, the Allure UAA and Allure Report services will need to re-initialize their databases.
The --set overrides in the command above disable the readiness and liveness probes for the services, which prevents Kubernetes from killing them due to timeouts.
Wait for the three deployments (allure-gateway, allure-report, allure-uaa) to become ready.

Use kubectl get all to view the status of the deployments and pods. When each pod becomes READY, the re-initialization of Allure Testops is completed.
Once the re-initialization is completed, enable the readiness and liveness probes that were disabled during installation. To do so, upgrade the chart once again, this time without the --set overrides.
```
helm upgrade allure-testops qameta/allure-testops --values values.yaml
```

Upgrade Allure Testops via Kubernetes

See also