28b9646616
Story: 2011080 Task: 50696 Change-Id: I0e816a2894c325d2b735eb879880b48ee23abc79 Signed-off-by: Juanita Balaraj <juanita.balaraj@windriver.com>
2.3 KiB
Upgrade the NetApp Trident Software
contains the installer for Trident 24.02, but installations that have been upgraded from the previous version and were configured to use a NetApp backend will still be running Trident 22.07 after the upgrade to .
[sysadmin@controller-0 trident(keystone_admin)]$ tridentctl -n trident version
+----------------+----------------+
| SERVER VERSION | CLIENT VERSION |
+----------------+----------------+
| 22.07 | 24.02 |
+----------------+----------------+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 24.02. 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:
Locate the
localhost.yamlfile that was used originally to install Trident, as described inConfigure an External NetApp Deployment as the Storage Backend <configure-an-external-netapp-deployment-as-the-storage-backend>.Add the line
trident_force_reinstall: trueto the file.Run the
install_netapp_backend.ymlplaybook again as per Run Playbook step of sectionConfigure an External NetApp Deployment as the Storage Backend <configure-an-external-netapp-deployment-as-the-storage-backend>.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 | +----------------+----------------+ | 22.07 | 24.02 | +----------------+----------------+