starlingx/docs
Code Issues Proposed changes
Files
ceae2adb3dc42f6477f8da19c891575e1661e161
docs/doc/source/storage/kubernetes/upgrade-the-netapp-trident-software-c5ec64d213d3.rst
Elisamara Aoki Gonçalves 5a4bd51488 Update Netapp Trident app 
Story: 2011379
Task: 52535

Change-Id: Ieb35a27952ac6a3f8b2daa1c17eec6aefb727c00
Signed-off-by: Elisamara Aoki Gonçalves <elisamaraaoki.goncalves@windriver.com>
2025-08-14 18:32:29 +00:00

2.3 KiB
Raw Blame History

Upgrade the NetApp Trident Software

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

[sysadmin@controller-0 trident(keystone_admin)]$ tridentctl -n trident version
+----------------+----------------+
| SERVER VERSION | CLIENT VERSION |
+----------------+----------------+
| 24.02.0        | 25.02.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.

Before upgrading Kubernetes to version , the running version of Trident must be updated to 25.02.1. 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 <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 <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 |
+----------------+----------------+
| 25.02.1        | 25.02.1        |
+----------------+----------------+