diff --git a/configuration/enable-offline-mode.adoc b/configuration/enable-offline-mode.adoc index 3662a3fce8d1..620ba0d27205 100644 --- a/configuration/enable-offline-mode.adoc +++ b/configuration/enable-offline-mode.adoc @@ -16,7 +16,7 @@ You can use {product-title} for clusters that are not connected to the internet To deploy and operate {product-title} in offline mode: -. Download {product-title-short} images and install them in your clusters. If you are using {ocp}, you can use link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html/operators/understanding-operators#operator-lifecycle-manager-olm[{olm-first}] and OperatorHub to download images to a workstation that is connected to the internet. The workstation then pushes images to a mirror registry that is also connected to your secured cluster. For other platforms, you can use a program such as Skopeo or Docker to pull the images from the remote registry and push them to your own private registry, as described in xref:../configuration/enable-offline-mode.adoc#download-images-for-offline-use[Downloading images for offline use]. +. Download {product-title-short} images and install them in your clusters. If you are using {ocp}, you can use link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.20/html/operators/understanding-operators#operator-lifecycle-manager-olm[{olm-first}] and the Software Catalog to download images to a workstation that is connected to the internet. The workstation then pushes images to a mirror registry that is also connected to your secured cluster. For other platforms, you can use a program such as Skopeo or Docker to pull the images from the remote registry and push them to your own private registry, as described in xref:../configuration/enable-offline-mode.adoc#download-images-for-offline-use[Downloading images for offline use]. . Enable offline mode during installation. . Update Scanner’s vulnerability list by uploading a new definitions file at least once per day. diff --git a/modules/compliance-operator-install.adoc b/modules/compliance-operator-install.adoc index e1a7669c8b28..928dd991d0d1 100644 --- a/modules/compliance-operator-install.adoc +++ b/modules/compliance-operator-install.adoc @@ -6,11 +6,11 @@ = Installing the Compliance Operator [role="_abstract"] -Install the Compliance Operator by using the Operator Hub. +Install the Compliance Operator by using the Software Catalog. .Procedure -. In the web console, go to the *Operators* -> *OperatorHub* page. +. In the web console, go to the *Ecosystem* -> *Software Catalog* page. . Enter *compliance operator* into the *Filter by keyword* box to find the Compliance Operator. diff --git a/modules/enable-monitoring-central-operator.adoc b/modules/enable-monitoring-central-operator.adoc index d13ec4e39fc9..5d0ca17be36a 100644 --- a/modules/enable-monitoring-central-operator.adoc +++ b/modules/enable-monitoring-central-operator.adoc @@ -9,7 +9,7 @@ You can monitor Central services, Central and Scanner, by changing the configuration of the `Central` custom resource. For more information on configuration options, see "Central configuration options using the Operator" in the "Additional resources" section. .Procedure -. On the {ocp} web console, go to the *Operators* -> *Installed Operators* page. +. On the {ocp} web console, go to the *Ecosystem* -> *Installed Operators* page. . Select the {product-title} Operator from the list of installed Operators. . Click on the *Central* tab. . From the list of Central instances, click on a Central instance for which you want to enable monitoring for. diff --git a/modules/enabling-scanner-v4-after-operator-installation-central.adoc b/modules/enabling-scanner-v4-after-operator-installation-central.adoc index c606892b1e11..f5c419f062e8 100644 --- a/modules/enabling-scanner-v4-after-operator-installation-central.adoc +++ b/modules/enabling-scanner-v4-after-operator-installation-central.adoc @@ -10,7 +10,7 @@ If Scanner V4 was not enabled during installation, you can enable it after insta .Procedure -. In the cluster where Central is installed, in the console, click *Operators* -> *Installed Operators* and select the {product-title-short} Operator. +. In the cluster where Central is installed, in the console, click *Ecosystem* -> *Installed Operators* and select the {product-title-short} Operator. . Click *Central* in the menu bar. . Click the name of the cluster where Central was installed. The default value is *stackrox-central-services*. . Click the *YAML* tab. diff --git a/modules/enabling-scanner-v4-after-operator-installation-secured-cluster.adoc b/modules/enabling-scanner-v4-after-operator-installation-secured-cluster.adoc index 188a92a1e4f1..3b2a034347bf 100644 --- a/modules/enabling-scanner-v4-after-operator-installation-secured-cluster.adoc +++ b/modules/enabling-scanner-v4-after-operator-installation-secured-cluster.adoc @@ -14,7 +14,7 @@ You can enable Scanner V4 after installation. .Procedure -. In the secured cluster, click *Operators* -> *Installed Operators* and select the {product-title-short} Operator. +. In the secured cluster, click *Ecosystem* -> *Installed Operators* and select the {product-title-short} Operator. . Click *Secured Cluster* in the menu bar. . Click the default cluster name, *stackrox-secured-cluster-services*, or the name that you entered during installation. . Click the *YAML* tab. diff --git a/modules/install-acs-operator-cloud.adoc b/modules/install-acs-operator-cloud.adoc index 489c2dd184f3..02a2f3a99482 100644 --- a/modules/install-acs-operator-cloud.adoc +++ b/modules/install-acs-operator-cloud.adoc @@ -7,16 +7,16 @@ = Installing the {product-title-short} Operator for {product-title-managed-short} [role="_abstract"] -Using the OperatorHub provided with {ocp} is the easiest way to install the {product-title-short} Operator. +Using the Software Catalog provided with {ocp} is the easiest way to install the {product-title-short} Operator. .Prerequisites * You have access to an {ocp} cluster using an account with Operator installation permissions. * You must be using {ocp} {ocp-supported-version} or later. For information about supported platforms and architecture, see the link:https://access.redhat.com/articles/7045053[{product-title} Support Matrix]. .Procedure -. In the web console, go to the *Operators* -> *OperatorHub* page. +. In the web console, go to the *Ecosystem* -> *Software Catalog* page. -. If {product-title} is not displayed, enter *Advanced Cluster Security* into the *Filter by keyword* box to find the {product-title} Operator. +. If {product-title} is not displayed, enter *Advanced Cluster Security* into the *Filter by keyword* box to find the {product-title} Operator. You might have to select a project first. . Select the *{product-title} Operator* to view the details page. @@ -36,4 +36,4 @@ Red{nbsp}Hat recommends enabling automatic upgrades for Operator in {product-tit . Click *Install*. .Verification -* After the installation completes, go to *Operators* -> *Installed Operators* to verify that the {product-title} Operator is listed with the status of *Succeeded*. +* After the installation completes, go to *Ecosystem* -> *Installed Operators* to verify that the {product-title} Operator is listed with the status of *Succeeded*. diff --git a/modules/install-acs-operator.adoc b/modules/install-acs-operator.adoc index 49363f243df8..bbc18949d1b1 100644 --- a/modules/install-acs-operator.adoc +++ b/modules/install-acs-operator.adoc @@ -7,16 +7,16 @@ = Installing the {product-title} Operator [role="_abstract"] -Using the OperatorHub provided with {ocp} is the easiest way to install {product-title}. +Using the Software Catalog provided with {ocp} is the easiest way to install {product-title}. .Prerequisites * You have access to an {ocp} cluster using an account with Operator installation permissions. * You must be using {ocp} {ocp-supported-version} or later. For information about supported platforms and architecture, see the link:https://access.redhat.com/articles/7045053[{product-title} Support Matrix]. For life cycle support information for {product-title-short}, see the link:https://access.redhat.com/support/policy/updates/rhacs[{product-title} Support Policy]. .Procedure -. In the web console, go to the *Operators* -> *OperatorHub* page. +. In the web console, go to the *Ecosystem* -> *Software Catalog* page. -. If {product-title} is not displayed, enter *Advanced Cluster Security* into the *Filter by keyword* box to find the {product-title} Operator. +. If {product-title} is not displayed, enter *Advanced Cluster Security* into the *Filter by keyword* box to find the {product-title} Operator. You might have to select a project first. . Select the *{product-title} Operator* to view the details page. @@ -40,6 +40,6 @@ If you choose manual updates, you must update the {product-title-short} Operator . Click *Install*. .Verification -* After the installation completes, go to *Operators* -> *Installed Operators* to verify that the {product-title} Operator is listed with the status of *Succeeded*. +* After the installation completes, go to *Ecosystem* -> *Installed Operators* to verify that the {product-title} Operator is listed with the status of *Succeeded*. After you install the Operator into the *rhacs-operator* project, you can install, configure, and deploy the `Central` custom resource (CR) into the `stackrox` project by using the installed Operator. \ No newline at end of file diff --git a/modules/install-central-operator-external-db.adoc b/modules/install-central-operator-external-db.adoc index da65880f9c66..7e9ea61580dc 100644 --- a/modules/install-central-operator-external-db.adoc +++ b/modules/install-central-operator-external-db.adoc @@ -26,7 +26,7 @@ Postgres 15 is the recommended and supported version. Red{nbsp}Hat has deprecate * For detailed requirements, see "Requirements for using an external database" in the additional resources section. .Procedure -. On the {ocp} web console, go to the *Operators* -> *Installed Operators* page. +. On the {ocp} web console, go to the *Ecosystem* -> *Installed Operators* page. . Select the {product-title} Operator from the list of installed Operators. . If you have installed the Operator in the recommended namespace, {ocp} lists the project as `rhacs-operator`. Select *Project: rhacs-operator* -> *Create project*. + diff --git a/modules/install-central-operator.adoc b/modules/install-central-operator.adoc index e695b0650f52..9b94c475f0e4 100644 --- a/modules/install-central-operator.adoc +++ b/modules/install-central-operator.adoc @@ -18,7 +18,7 @@ The main component of {product-title} is called Central. You can install Central * You must be using {ocp} {ocp-supported-version} or later. For information about supported platforms and architecture, see the link:https://access.redhat.com/articles/7045053[{product-title} Support Matrix]. For life cycle support information for {product-title-short}, see the link:https://access.redhat.com/support/policy/updates/rhacs[{product-title} Support Policy]. .Procedure -. On the {ocp} web console, go to the *Operators* -> *Installed Operators* page. +. On the {ocp} web console, go to the *Ecosystem* -> *Installed Operators* page. . Select the {product-title} Operator from the list of installed Operators. . If you have installed the Operator in the recommended namespace, {ocp} lists the project as `rhacs-operator`. Select *Project: rhacs-operator* -> *Create project*. + diff --git a/modules/install-secured-cluster-operator.adoc b/modules/install-secured-cluster-operator.adoc index af88497ea9d3..13a2e2bddf31 100644 --- a/modules/install-secured-cluster-operator.adoc +++ b/modules/install-secured-cluster-operator.adoc @@ -30,7 +30,7 @@ When you install {product-title}: * You have generated an init bundle or cluster registration secret (CRS) and applied it to the cluster in the recommended `stackrox` namespace. .Procedure -. On the {ocp} web console for the secured cluster, go to the *Operators* -> *Installed Operators* page. +. On the {ocp} web console for the secured cluster, go to the *Ecosystem* -> *Installed Operators* page. . Click the {product-title-short} Operator. . If you have installed the Operator in the recommended namespace, {ocp} lists the project as `rhacs-operator`. + diff --git a/modules/monitor-osp-disable-operator.adoc b/modules/monitor-osp-disable-operator.adoc index ea4e6ffb5575..353eff6f1c41 100644 --- a/modules/monitor-osp-disable-operator.adoc +++ b/modules/monitor-osp-disable-operator.adoc @@ -8,7 +8,7 @@ To disable the default monitoring by using the Operator, change the configuration of the `Central` custom resource as shown in the following example. For more information on configuration options, see "Central configuration options using the Operator" in the "Additional resources" section. .Procedure -. On the {ocp} web console, go to the *Operators* -> *Installed Operators* page. +. On the {ocp} web console, go to the *Ecosystem* -> *Installed Operators* page. . Select the {product-title-short} Operator from the list of installed Operators. . Click on the *Central* tab. . From the list of Central instances, click on a Central instance for which you want to enable monitoring. diff --git a/modules/operator-upgrade-change-subscription-channel.adoc b/modules/operator-upgrade-change-subscription-channel.adoc index b6628de66617..e0d4bbdd4b7d 100644 --- a/modules/operator-upgrade-change-subscription-channel.adoc +++ b/modules/operator-upgrade-change-subscription-channel.adoc @@ -34,12 +34,12 @@ endif::[] Use the following instructions for changing the subscription channel by using the web console: .Procedure -. In the *Administrator* perspective of the {ocp} web console, go to *Operators* → *Installed Operators*. +. In the *Administrator* perspective of the {ocp} web console, go to *Ecosystem* → *Installed Operators*. . Click the {product-title-short} 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 an *Automatic* approval strategy, the update begins automatically. Go back to the *Ecosystem* → *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. diff --git a/modules/rollback-operator-upgrades-cli.adoc b/modules/rollback-operator-upgrades-cli.adoc index f829221f68ec..ad737302798f 100644 --- a/modules/rollback-operator-upgrades-cli.adoc +++ b/modules/rollback-operator-upgrades-cli.adoc @@ -53,7 +53,7 @@ clusterserviceversion.operators.coreos.com "rhacs-operator.v4.8.4" deleted ifndef::cloud-svc[] . Install the previous version of the {product-title-short} Operator: -.. In the OpenShift web console, click *OperatorHub*. +.. In the OpenShift web console, click *Ecosystem* -> *Software Catalog*. .. Search for *Advanced Cluster Security for Kubernetes*. .. Select and install the previous version of the Operator. + diff --git a/modules/rollback-operator-upgrades-console.adoc b/modules/rollback-operator-upgrades-console.adoc index 50a09f3d176d..5db892096316 100644 --- a/modules/rollback-operator-upgrades-console.adoc +++ b/modules/rollback-operator-upgrades-console.adoc @@ -19,7 +19,7 @@ You can roll back the Operator version by using the {ocp} web console. .Procedure -. In the OpenShift web console, click *Operators* -> *Installed Operators*. +. In the OpenShift web console, click *Ecosystem* -> *Installed Operators*. . From the list of projects, select *rhacs-operator*. . Locate the *Advanced Cluster Security for Kubernetes* Operator: .. Click the overflow menu {kebab} -> *Uninstall Operator*. @@ -30,7 +30,7 @@ The uninstall Operator dialog is displayed. ifndef::cloud-svc[] . Install the previous version of {product-title-short} Operator: -.. In the OpenShift web console, click *OperatorHub*. +.. In the OpenShift web console, click *Ecosystem* -> *Installed Operators*. .. Search for *Advanced Cluster Security for Kubernetes*. .. Select and install the previous version of the Operator. + diff --git a/modules/verify-central-install-operator.adoc b/modules/verify-central-install-operator.adoc index 29cec1c52058..36d39c5cbb02 100644 --- a/modules/verify-central-install-operator.adoc +++ b/modules/verify-central-install-operator.adoc @@ -8,7 +8,7 @@ After Central finishes installing, log in to the {product-title-short} portal to verify the successful installation of Central. .Procedure -. On the {ocp} web console, go to the *Operators* -> *Installed Operators* page. +. On the {ocp} web console, go to the *Ecosystem* -> *Installed Operators* page. . Select the {product-title} Operator from the list of installed Operators. . Select the *Central* tab. . From the *Centrals* list, select `stackrox-central-services` to view its details.