1.4. Changing the subscription channel
You can change the update channel for the RHACS Operator by using the OpenShift Container Platform web console or by using the command line. For upgrading to RHACS 4.0 from RHACS 3.74, you must change the update channel.
- You must change the subscription channel for all clusters where you installed the RHACS Operator, including Central and all secured clusters.
-
If you use Kubernetes, enter
kubectlinstead ofoc.
Prerequisites
- You must verify that you are using the latest RHACS 3.74 Operator and there are no pending manual Operator upgrades.
- You must verify that you backed up your Central database.
-
You have access to an OpenShift Container Platform cluster web console using an account with
cluster-adminpermissions.
Use the following instructions for changing the subscription channel by using the web console:
Procedure
-
In the Administrator perspective of the OpenShift Container Platform web console, go to Operators
Installed Operators. - Click the RHACS Operator.
- Click the Subscription tab.
- Click the name of the update channel under Update Channel.
- Select stable, then click Save.
For subscriptions with an Automatic approval strategy, the update begins automatically. Go back to the Operators
Installed Operators page to monitor the progress of the update. When complete, the status changes to Succeeded and Up to date. For subscriptions with a Manual approval strategy, you can manually approve the update from the Subscription tab.
Use the following instructions for changing the subscription channel by using command line:
Procedure
Run the following command to change the subscription channel to
stable:$ oc -n rhacs-operator \ patch subscriptions.operators.coreos.com rhacs-operator \ --type=merge --patch='{ "spec": { "channel": "stable" }}'During the update, the RHACS Operator provisions a new deployment called
central-dband your data begins migrating. It takes around 30 minutes and happens only after you upgrade.