Merge "Updated NetApp Trident Version for Kubernetes"

This commit is contained in:
Zuul 2024-08-01 14:24:53 +00:00 committed by Gerrit Code Review
commit 92b879bbec
6 changed files with 28 additions and 27 deletions

View File

@ -6,9 +6,9 @@ Upgrade the NetApp Trident Software
.. rubric:: |context|
|prod| |prod-ver| contains the installer for Trident 22.07, but installations
|prod| |prod-ver| contains the installer for Trident 24.02, 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 use a NetApp backend will still be running Trident 22.07 after the upgrade
to |prod| |prod-ver|.
.. code-block:: none
@ -17,7 +17,7 @@ to |prod| |prod-ver|.
+----------------+----------------+
| SERVER VERSION | CLIENT VERSION |
+----------------+----------------+
| 20.04.0 | 21.04.1 |
| 22.07 | 24.02 |
+----------------+----------------+
.. note::
@ -33,7 +33,7 @@ to |prod| |prod-ver|.
.. rubric:: |proc|
Before upgrading Kubernetes to version |kube-ver|, the running version of Trident
must be updated to 22.07. This will not disrupt any containers that are already
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:
@ -58,5 +58,5 @@ The steps are as follows:
+----------------+----------------+
| SERVER VERSION | CLIENT VERSION |
+----------------+----------------+
| 21.01 | 22.07 |
| 22.07 | 24.02 |
+----------------+----------------+

View File

@ -48,7 +48,7 @@ meets the following conditions:
- If you are using NetApp Trident in |prod| |prod-ver| and have upgraded from
the |prod| previous version, ensure that your NetApp backend version is
compatible with Trident 22.07 and follow the steps in :ref:`Upgrade the
compatible with Trident 24.02 and follow the steps in :ref:`Upgrade the
NetApp Trident Software <upgrade-the-netapp-trident-software-c5ec64d213d3>`
to upgrade the Trident drivers to 22.07 before upgrading Kubernetes to
version |kube-ver|.

View File

@ -71,7 +71,7 @@ For example:
- Hosts that need to be upgraded must be in the **unlocked-enabled** state.
- If you are using NetApp Trident, ensure that your NetApp version is
compatible with Trident 22.07 before upgrading Kubernetes to version
compatible with Trident 24.02 before upgrading Kubernetes to version
|kube-ver| and after updating |prod| to version |prod-ver|. For more
information, see :ref:`upgrade-the-netapp-trident-software-c5ec64d213d3`.
@ -81,7 +81,7 @@ For example:
.. rubric:: |proc|
#. List available upgrades.
#. List available upgrades, for example:
.. code-block:: none
@ -356,4 +356,4 @@ For example:
.. code-block:: none
~(keystone_admin)$ sw-manager kube-upgrade-strategy delete
Strategy deleted.
Strategy deleted.

View File

@ -75,7 +75,7 @@ For example:
- Hosts that need to be upgraded must be in the ``unlocked-enabled`` state.
- If you are using NetApp Trident, ensure that your NetApp version is
compatible with Trident 22.07 before upgrading Kubernetes to version
compatible with Trident 24.02 before upgrading Kubernetes to version
|kube-ver| and after updating |prod| to version |prod-ver|. For more
information, see :ref:`Upgrade the NetApp Trident Software
<upgrade-the-netapp-trident-software-c5ec64d213d3>`.
@ -88,7 +88,7 @@ For example:
.. rubric:: |proc|
#. List available upgrades.
#. List available upgrades, for example:
.. code-block:: none
@ -202,7 +202,7 @@ For example:
specify the maximum worker hosts to upgrade in parallel (minimum: 2,
maximum: 10).
``instance-action``
``-instance-action``
This option only has significance when the |prefix|-openstack
application is loaded and there are instances running on worker hosts.
It specifies how the strategy deals with worker host instances over the
@ -331,7 +331,7 @@ For example:
- Use the :command:`kube-upgrade-show` command to monitor Kubernetes
upgrade state and percentage completion.
upgrade state and percentage completion, for example:
.. code-block:: none
@ -359,7 +359,7 @@ For example:
used to abort the Kubernetes version upgrade strategy after the current
step of the currently applying stage is completed.
#. Confirm that the upgrade has completed successfully.
#. Confirm that the upgrade has completed successfully, for example:
.. code-block:: none

View File

@ -54,10 +54,10 @@ and upgrade various systems.
- If you are using NetApp Trident in |prod| |prod-ver| and have upgraded from
the |prod| previous version, ensure that your NetApp backend version is
compatible with Trident 22.07 and follow the steps in :ref:`Upgrade the
compatible with Trident 24.02 and follow the steps in :ref:`Upgrade the
NetApp Trident Software <upgrade-the-netapp-trident-software-c5ec64d213d3>`
to upgrade the Trident drivers to 21.04 before upgrading Kubernetes to
version 1.19.
to upgrade the Trident drivers to 24.02 before upgrading Kubernetes to
version 1.29.
.. rubric:: |proc|
@ -68,7 +68,8 @@ and upgrade various systems.
#. List the available Kubernetes versions.
On a fresh install of |prod| |prod-ver|, the following output appears:
On a fresh install of |prod| |prod-ver|, the following output appears, for
example:
.. code-block:: none
@ -208,7 +209,7 @@ and upgrade various systems.
~(keystone_admin)]$ system kube-pre-application-update
#. Upgrade Kubernetes networking.
#. Upgrade Kubernetes networking, for example:
.. code-block:: none
@ -227,7 +228,7 @@ and upgrade various systems.
The state *upgraded-networking* will be entered when the networking
upgrade has completed.
#. Upgrade the storage.
#. Upgrade the storage, for example:
.. code-block:: none
@ -246,7 +247,7 @@ and upgrade various systems.
The state ``upgraded-storage`` will be entered when the storage upgrade has
completed.
#. Upgrade the control plane on the first controller.
#. Upgrade the control plane on the first controller, for example:
.. code-block:: none
@ -268,7 +269,7 @@ and upgrade various systems.
The state *upgraded-first-master* will be entered when the first control
plane upgrade has completed.
#. Upgrade the control plane on the second controller.
#. Upgrade the control plane on the second controller, for example:
.. code-block:: none
@ -288,7 +289,7 @@ and upgrade various systems.
The state *upgraded-second-master* will be entered when the upgrade has
completed.
#. Show the Kubernetes upgrade status for all hosts.
#. Show the Kubernetes upgrade status for all hosts, for example:
.. code-block:: none

View File

@ -38,13 +38,13 @@ system. This feature is not supported in the system which is not |AIO-SX|.
- If you are using NetApp Trident in |prod| |prod-ver| and if you have
upgraded from the |prod| previous version, ensure that your NetApp backend
version is compatible with Trident 22.07. Follow the steps in
version is compatible with Trident 24.02. Follow the steps in
:ref:`upgrade-the-netapp-trident-software-c5ec64d213d3` to upgrade Trident
to 22.07 before upgrading Kubernetes to version 1.24.
to 24.02 before upgrading Kubernetes to version 1.29.
.. rubric:: |proc|
#. List the available Kubernetes versions.
#. List the available Kubernetes versions, for example:
On a fresh install of |prod| |prod-ver|, the following output appears:
@ -183,7 +183,7 @@ system. This feature is not supported in the system which is not |AIO-SX|.
~(keystone_admin)]$ system kube-pre-application-update
#. Upgrade Kubernetes networking.
#. Upgrade Kubernetes networking, for example:
.. code-block:: none