mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 00:48:01 +01:00
113 lines
3.6 KiB
Plaintext
113 lines
3.6 KiB
Plaintext
// CNF-296 Performance Addon Operator Upgrades
|
|
// CNF-763 - Write a d/s upgrade guide for Performance Add-on Operator
|
|
//Upgrading Performance Addon Operator
|
|
// CNF 4.5
|
|
// *.adoc
|
|
//
|
|
|
|
[IMPORTANT]
|
|
====
|
|
The feature described in this document is for *Developer Preview* purposes and is *not supported* by Red Hat at this time.
|
|
This feature could cause nodes to reboot and not be available.
|
|
====
|
|
|
|
[id="upgrading-performance-addon-operator_{context}"]
|
|
= Upgrading Performance Addon Operator
|
|
|
|
You can manually upgrade to the next minor version of Performance Addon Operator and monitor the status of an update
|
|
by using the web console.
|
|
|
|
== About upgrading Performance Addon Operator
|
|
|
|
=== How Performance Addon Operator upgrades work
|
|
|
|
* You can upgrade to the next minor version of Performance Addon Operator by using the OpenShift web
|
|
console to change the channel of your Operator subscription.
|
|
|
|
* You can enable automatic z-stream updates during Performance Addon Operator installation.
|
|
|
|
* Updates are delivered via the Marketplace Operator, which is deployed during {product-title} installation.
|
|
The Marketplace Operator makes external Operators available to your cluster.
|
|
|
|
* The amount of time an update takes to complete depends on your network connection.
|
|
Most automatic updates complete within fifteen minutes.
|
|
|
|
=== How Performance Addon Operator upgrades affect your cluster
|
|
|
|
* Neither the low latency tuning nor huge pages are affected.
|
|
|
|
* Updating the Operator should not cause any unexpected reboots.
|
|
|
|
=== Upgrading Performance Addon Operator to the next minor version
|
|
|
|
You can manually upgrade Performance Addon Operator to the next minor version by using the {product-title}
|
|
web console to change the channel of your Operator subscription.
|
|
|
|
.Prerequisites
|
|
|
|
* Access to the cluster as a user with the cluster-admin role.
|
|
|
|
.Procedure
|
|
|
|
. Access the OpenShift web console and navigate to *Operators → Installed Operators*.
|
|
|
|
. Click *Performance Addon Operator* to open the *Operator Details* page.
|
|
|
|
. Click the *Subscription* tab to open the *Subscription Overview* page.
|
|
|
|
. In the *Channel* pane, click the pencil icon on the right side of the version number to open the *Change Subscription
|
|
Update Channel* window.
|
|
|
|
. Select the next minor version. For example, if you want to upgrade to Performance Addon Operator 4.5, select *4.5*.
|
|
|
|
. Click *Save*.
|
|
|
|
. Check the status of the upgrade by navigating to *Operators → Installed Operators*.
|
|
You can also check the status by running the following `oc` command:
|
|
+
|
|
----
|
|
$ oc get csv -n openshift-performance-addon-operator
|
|
----
|
|
|
|
== Monitoring upgrade status
|
|
The best way to monitor Performance Addon Operator upgrade status is to watch the ClusterServiceVersion (CSV) `PHASE`.
|
|
You can also monitor the CSV conditions in the web console or by running the command provided here.
|
|
|
|
[NOTE]
|
|
====
|
|
The `PHASE` and conditions values are approximations that are based on available information.
|
|
====
|
|
|
|
.Prerequisites
|
|
|
|
* Access to the cluster as a user with the `cluster-admin` role.
|
|
|
|
* Install the OpenShift CLI (`oc`).
|
|
|
|
.Procedure
|
|
|
|
. Run the following command:
|
|
+
|
|
----
|
|
$ oc get csv
|
|
----
|
|
|
|
. Review the output, checking the `PHASE` field. For example:
|
|
+
|
|
----
|
|
VERSION REPLACES PHASE
|
|
4.5.0 performance-addon-operator.v4.4.0 Installing
|
|
4.4.0 Replacing
|
|
----
|
|
|
|
. Run `get csv` again to verify the output:
|
|
+
|
|
----
|
|
# oc get csv
|
|
----
|
|
|
|
----
|
|
NAME DISPLAY VERSION REPLACES PHASE
|
|
performance-addon-operator.v4.5.0 Performance Addon Operator 4.5.0 performance-addon-operator.v4.4.0 Succeeded
|
|
----
|