Upgrading Saagie

Use this tutorial to upgrade to a newer version of Saagie atop an existing installation.

When upgrading Saagie, do not delete the previous installation folder to keep the history of previously installed versions. This could be useful for Saagie support in future upgrades.

Upgrading Saagie to the Latest Version

Open a ticket on the Saagie Help Center to contact our SRE team to get the latest Saagie installer. For more information, see How can I contact Saagie support?.

Do not merge the content of this installer with the previous installation folder. To do so, unzip it in a new folder.
Copy and paste the .mdl and .yml files from your previous installation folder into the newest installation folder that you just unzip.
Launch the installer by running the following command:
```
./bin/saagiectl configure
```
You may have to respond to a new series of prompts. A new parameter in a section will lead you to respond to all the prompts in that section.

Be sure to reconfigure your product with the same answers as before. For more information, see how to configure Saagie.
Validate your environment to make sure it meets all requirements by running the following command:
```
./bin/saagiectl validate all
```
If your environment does not pass validation, submit a ticket to Saagie support.
Run the following command to upgrade Saagie:
```
./bin/saagiectl upgrade
```

Upgrading Saagie to Version 2024.02

Use this procedure only if you want to upgrade to Saagie 2024.02.

Open a ticket on the Saagie Help Center to contact our SRE team to get version 2024.02 of the Saagie installer. For more information, see How can I contact Saagie support?.

Do not merge the content of this installer with the previous installation folder. To do so, unzip it in a new folder.
Copy and paste the .mdl and .yml files from your previous installation folder into the newest installation folder that you just unzip.
Launch the installer by running the following command:
```
./bin/saagiectl configure
```
You may have to respond to a new series of prompts. A new parameter in a section will lead you to respond to all the prompts in that section.

Be sure to reconfigure your product with the same answers as before. For more information, see how to configure Saagie.
Validate your environment to make sure it meets all requirements by running the following command:
```
./bin/saagiectl validate all
```
If your environment does not pass validation, submit a ticket to Saagie support.

Launch the following code snippet before upgrading Saagie:

export INSTALLATION_ID=

kubectl -n $INSTALLATION_ID-pf1 label pvc minio io.saagie/installationId=$INSTALLATION_ID
kubectl -n $INSTALLATION_ID-pf1 label secret saagie-docker-config io.saagie/installationId=$INSTALLATION_ID
kubectl -n $INSTALLATION_ID-pf1 label secret minio io.saagie/installationId=$INSTALLATION_ID
kubectl -n $INSTALLATION_ID-pf1 label secret minio-read io.saagie/installationId=$INSTALLATION_ID

kubectl -n $INSTALLATION_ID-pf2 label pvc minio io.saagie/installationId=$INSTALLATION_ID
kubectl -n $INSTALLATION_ID-pf2 label secret saagie-docker-config io.saagie/installationId=$INSTALLATION_ID
kubectl -n $INSTALLATION_ID-pf2 label secret minio io.saagie/installationId=$INSTALLATION_ID
kubectl -n $INSTALLATION_ID-pf2 label secret minio-read io.saagie/installationId=$INSTALLATION_ID

Where:

<installationId> must be replaced with your installation ID. It must match the prefix you have determined for your DNS entry.

Run the following command to upgrade Saagie:
```
./bin/saagiectl upgrade
```

Launch the following code snippet after upgrading Saagie:

export INSTALLATION_ID=

# Stop Prometheus observability
kubectl -n $INSTALLATION_ID scale deployment --replicas=0 saagie-common-observability-prometheus-server
# Replace data from old PVC to new PVC
kubectl pv-migrate migrate -n $INSTALLATION_ID -N $INSTALLATION_ID saagie-common-observability-prometheus saagie-common-observability-prometheus-server -d
# Restart Prometheus
kubectl -n $INSTALLATION_ID scale deployment --replicas=1 saagie-common-observability-prometheus-server

export INSTALLATION_ID=

# Remove useless UMDC and check URLs
kubectl delete cronjob -n $INSTALLATION_ID umdc-agent
kubectl delete job -n $INSTALLATION_ID checker-urls

Where:

<installationId> must be replaced with your installation ID. It must match the prefix you have determined for your DNS entry.