Upgrading the server software on Azure Kubernetes Service

When you want to use the latest version of the server software on Azure Kubernetes Service (AKS), you must upgrade Rational® Test Automation Server from the previous version of the software.

Before you begin

You must have read and been familiar with additional Helm parameters. See Additional Helm parameters.
You must have completed the following tasks:
- Completed the tasks provided in the Prerequisites section. See Prerequisites for installing the server software on Azure Kubernetes Service.
- Installed Emissary-ingress. See Installing Emissary-ingress.
- Informed users that Rational® Test Automation Server is offline temporarily during the upgrade process.
- Completed all test executions that are running on the existing version of Rational® Test Automation Server.
- Stopped all stub executions that are running on the existing version of Rational® Test Automation Server.
- Canceled any scheduled test runs that have a future date or time.
- Logged in to the AKS cluster.
  
  Note: You can run the az login command to log in to AKS interactively.
- Subscribed to active Azure subscription.
  
  Note: You can run the az account set --subscription {subscription_name} command to set your active subscription.

Optional. You can back up the user data from the earlier version of the product. If the upgrade fails, then you can use that backup file to restore it to the latest version of the server software. See Backing up the server data on Azure Kubernetes Service.

Note: For more information about specific versions of software requirements, see System Requirements.

About this task

When you want to install the latest version of the server software in the same location that contained the 10.2.3 or later, then you can upgrade Rational® Test Automation Server by using the helm upgrade command.

The following table lists the variables that you must replace with the actual value in the command.

Variables	Description
{resource_group}	The name of the resource group that you created during the creation of the AKS cluster.
{azure_cluster}	The name of the Azure cluster that you created during the creation of the AKS cluster.
{azure_container_registry}	The name of the ACR that you created during the AKS setup.
{my-ingress-dns-name}	The Ingress name and DNS zone value that you provided during the setting up of the AKS cluster. For example, if the Ingress name and DNS zone value that you provided are `rationaltest`, `myorg.nonprod`, then `{my-ingress-dns-name}` value must be `rationaltest.myorg.nonprod`.
{my-rtas}	The release name that you provided during the installation of the server software.

Remember: The test-system is the name of the namespace that you created during the installation of the server software. If you created a namespace by using a different value, then you must use that value in place of test-system in all the instances in this procedure.

Tip: You can run the following command to know the value of the variables that you used during the installation of the previous version of the server software:

helm get values {release_name} -n {namespace}

For example, if your name of the release is my-rtas and the name of the namespace is testsystem, then you must run the command as follows:

helm get values my-rtas -n testsystem

Procedure

Add the entitlement registry to Helm by running the following command:

helm repo add ibm-helm https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm

Run the following command to get the latest updates from the repository:
```
helm repo update
```
Run the following commands to fetch the scripts that are used to install Rational® Test Automation Server:
```
helm pull --untar ibm-helm/ibm-rtas-prod --version 9.1050.0
```
Run the following command to configure kubectl to connect to the AKS cluster:
```
az aks get-credentials -g {resource_group} -n {azure_cluster}
```
Note: You can verify the connection to the AKS cluster by running the kubectl get nodes command that displays a list of the cluster nodes.
Run the following script from the ibm-rtas-prod/files directory to pull the images of Rational® Test Automation Server from the entitlement registry to ACR:
```
PULL_ARGUMENTS="-u cp -p {your_entitlement_key}" \
  bash ibm-rtas-prod/files/move-images.sh $REGISTRY.azurecr.io/ibm-rtas cp.icr.io/cp
```
Tip: You can verify that multiple manifests are associated with the image in the ACR by running the following commands:
```
az acr repository list -n {azure_container_registry} -otsv
az acr repository show-manifests -n {azure_container_registry} --repository \
$(az acr repository list -n {azure_container_registry} -otsv --query [0])
```
Run the helm list -A command to list all releases that are deployed across all namespaces.

Run the following command to upgrade the server software:

helm upgrade {my-rtas} ./ibm-rtas-prod -n test-system \
--set license=true \
-f ibm-rtas-prod/values-k8s.yaml \
--set global.persistence.rwxStorageClass=azurefile \
--set global.ibmRtasIngressDomain={my-ingress-dns-name} \
--set global.ibmRtasRegistry=<azure_container_registry>.azurecr.io/ibm-rtas \
--set global.ibmRtasPasswordAutoGenSeed={password-seed}

Note: The following command upgrades the server software by referencing the images from ACR. Therefore, Rational® Test Automation Server can provide better performance.

Run the following script from the ibm-rtas-prod/files directory to verify and test the installed server software:
```
ibm-rtas-prod/files/helm-test-diag.sh {my-rtas} -n test-system
```

Results

On the successful upgrade of Rational® Test Automation Server, the output displays the following information:

Keycloak URL to manage and authenticate users.
A URL to access the Rational® Test Automation Server UI.

What to do next

Configure licenses for team spaces. See Configuring licenses for team spaces.
Configure the server software. See Configuration of the server software.