Upgrading Virtalis Reach from Version 2023.1.0 to 2023.2.0

Introduction

This document is designed to help a systems administrator upgrade Virtalis Reach to the next available version

Set Up Variables

Export the following variables:


export REACH_NAMESPACE=reach
export REACH_VERSION=2023.2.0
export SKIP_MIGRATIONS=0
export ACR_REGISTRY_NAME=$(kubectl get secret reach-install-config -n $REACH_NAMESPACE -o json | jq ".data.ACR_REGISTRY_NAME" -r | base64 -d)
export ACR_USERNAME=$(kubectl get secret reach-install-config -n $REACH_NAMESPACE -o json | jq ".data.ACR_USERNAME" -r | base64 -d)
export ACR_PASSWORD=$(kubectl get secret reach-install-config -n $REACH_NAMESPACE -o json | jq ".data.ACR_PASSWORD" -r | base64 -d)

Download Installation Files

Log in with Oras:


oras login "${ACR_REGISTRY_NAME}".azurecr.io \
--username "${ACR_USERNAME}" \
-p "${ACR_PASSWORD}"

Make a backup of the old installation files:


sudo mv /home/root/Reach /home/root/.Reach

Make a directory to store installation files:


sudo mkdir -p /home/root/Reach && \
cd /home/root/Reach && \
sudo chown $(whoami) /home/root/Reach 

Pull the Kubernetes deployment file archive from the Virtalis registry and unzip it:


oras pull "${ACR_REGISTRY_NAME}".azurecr.io/misc/k8s:$REACH_VERSION && tar -zxvf k8s.tar.gz

Make the installation scripts executable:


cd k8s && sudo chmod +x *.sh && sudo chmod +x misc/keycloak/migration/*.sh

Installation

Clear old session data


kubectl wait pod/collaboration-session-db-mysql-master-0 -n $REACH_NAMESPACE --for=condition=ready
kubectl exec collaboration-session-db-mysql-master-0 -n $REACH_NAMESPACE -- /bin/bash -c 'rm -rf /bitnami/mysql/data; kill 1'

Load Previous Configuration


. ./load-install-config.sh

Create Secrets


./create-secrets.sh

Deploy Virtalis Reach


./deploy.sh
Print page
2022.2
October 17, 2023 8:26

Need more?