Upgrade the NetApp Trident Software

About this task

StarlingX r7.0 contains the installer for Trident 22.01, but installations that have been upgraded from the previous StarlingX version and were configured to use a NetApp backend will still be running Trident 21.04 after the upgrade to StarlingX r7.0.

[sysadmin@controller-0 trident(keystone_admin)]$ tridentctl -n trident version
+----------------+----------------+
| SERVER VERSION | CLIENT VERSION |
+----------------+----------------+
| 20.04.0        | 21.04.1        |
+----------------+----------------+

Note

In the table above, the client version refers to the binary (tridentctl) and the server version refers to the services installed in Kubernetes.

This difference between versions only occurs during the upgrade, as the client version will be upgraded, but the server version will be the current version at this point.

Procedure

Before upgrading Kubernetes to version 1.23.1, the running version of Trident must be updated to 22.01. This will not disrupt any containers that are already running, but will cause a brief outage to the NetApp Trident control plane.

The steps are as follows:

1. Locate the localhost.yaml file that was used originally to install Trident, as described in Configure an External NetApp Deployment as the Storage Backend.

2. Add the line trident_force_reinstall: true to the file.

3. Run the install_netapp_backend.yml playbook again as per Run Playbook step of section Configure an External NetApp Deployment as the Storage Backend.

4. On completion, verify that the Trident server version has been updated:

   [sysadmin@controller-0 trident(keystone_admin)]$ tridentctl -n trident version
   +----------------+----------------+
   | SERVER VERSION | CLIENT VERSION |
   +----------------+----------------+
   | 21.01          | 22.01          |
   +----------------+----------------+