docs/doc/source/storage/kubernetes/upgrade-the-netapp-trident-software-c5ec64d213d3.rst
Ron Stone 0fe8d64538 Container Components Refresh for k8s - v1.23
Bump trident version to 22.01
Add placeholder for k8s 1.23.1

Depends-On: https://review.opendev.org/c/starlingx/docs/+/840219

Story: 2009830
Task: 45233

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I9fc8b9b4c5a56e2319e2a36b049de7d23bf253e2
2022-05-02 13:40:43 -04:00

63 lines
2.3 KiB
ReStructuredText

.. _upgrade-the-netapp-trident-software-c5ec64d213d3:
===================================
Upgrade the NetApp Trident Software
===================================
.. rubric:: |context|
|prod| |prod-ver| contains the installer for Trident 22.01, but installations
that have been upgraded from the previous |prod| version and were configured
to use a NetApp backend will still be running Trident 21.04 after the upgrade
to |prod| |prod-ver|.
.. code-block:: none
[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.
.. rubric:: |proc|
Before upgrading Kubernetes to version |kube-ver|, 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:
#. Locate the ``localhost.yaml`` file that was used originally to install
Trident, as described in :ref:`Configure an External NetApp Deployment as
the Storage Backend
<configure-an-external-netapp-deployment-as-the-storage-backend>`.
#. Add the line ``trident_force_reinstall: true`` to the file.
#. Run the ``install_netapp_backend.yml`` playbook again as per Run Playbook
step of section :ref:`Configure 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:
.. code-block:: none
[sysadmin@controller-0 trident(keystone_admin)]$ tridentctl -n trident version
+----------------+----------------+
| SERVER VERSION | CLIENT VERSION |
+----------------+----------------+
| 21.01 | 22.01 |
+----------------+----------------+