13.2. Enabling Scanner V4

Procedure

1. On the cluster where Central is installed, follow the installation procedures as described in "Installing Central using the Operator method". Choose one of these methods to enable Scanner V4:

   • As described in that procedure, when configuring the available options for Central, go to the Scanner V4 Component Settings section and in the Scanner V4 Component menu, select Enabled.

   • In the Central custom resource (CR) YAML, configure the following parameter:

       scannerV4:
         scannerComponent: Enabled

2. Configure your init bundle or cluster registration secret (CRS) to allow communication between Central and the secured cluster. For more information, see "Generating and applying an init bundle or cluster registration secret for RHACS on Red Hat OpenShift".

Procedure

1. On the secured cluster, follow the installation procedures as described in "Installing RHACS on secured clusters by using the Operator". Choose one of these methods to enable Scanner V4:

   • In the Scanner V4 Component Settings section, in the Scanner V4 Component menu, select AutoSense.

   • In the SecuredCluster CR YAML, configure the following parameter:

       scannerV4:
         scannerComponent: AutoSense

Procedure

1. On the cluster where Central is installed, run the following command, using the instructions in "Install Central using Helm charts with customizations" if you need more information:

   $ helm install -n stackrox --create-namespace \
       stackrox-central-services rhacs/central-services \
       --set scannerV4.disable=false \
       -f <path_to_values_public.yaml> -f <path_to_values_private.yaml>

   Example output

   Central Services Configuration Summary:
   
       Stackrox Version:                            4.7.1
       Kubernetes Version:                          v1.31.6
       Kubernetes Namespace:                        stackrox
       Helm Release Name:                           stackrox-central-services
       OpenShift Cluster:                           4
       Scanner V4:                                  enabled
       Scanner V4 DB Volume:                        PVC (scanner-v4-db)

2. Configure your init bundle or cluster registration secret (CRS) so that Central and the secured cluster can communicate. For more information, see "Generating and applying an init bundle or cluster registration secret for RHACS on Red Hat OpenShift" or "Generating and applying an init bundle or cluster registration secret for RHACS on other platforms".

Procedure

1. On the secured cluster, run the following command, using the instructions in "Configuring the secured-cluster-services Helm chart with customizations" if you need more information:

   $ helm install -n stackrox --create-namespace \
       stackrox-secured-cluster-services rhacs/secured-cluster-services \
       --set-file crs.file=<crs_file_name.yaml> \
       -f <path_to_pull_secret.yaml> \
       -f <path_to_values_public.yaml> -f <path_to_values_private.yaml> \
       --set clusterName=<name_of_the_secured_cluster> \
       --set centralEndpoint=<endpoint_of_central_service> \
       --set scanner.disable=false \
       --set scannerV4.disable=false

Procedure

1. In the cluster where Central is installed, in the console, click Operators Installed Operators and select the RHACS Operator.
2. Click Central in the menu bar.
3. Click the name of the cluster where Central was installed. The default value is stackrox-central-services.
4. Click the YAML tab.

5. Edit the YAML file as shown in the following example:

     scannerV4:
       scannerComponent: Enabled

Procedure

1. In the secured cluster, click Operators Installed Operators and select the RHACS Operator.
2. Click Secured Cluster in the menu bar.
3. Click the default cluster name, stackrox-secured-cluster-services, or the name that you entered during installation.
4. Click the YAML tab.

5. Edit the YAML file as shown in the following example:

     scannerV4:
       scannerComponent: AutoSense

Procedure

1. On the cluster where Central is installed, run the following command, using the instructions in "Changing configuration options after deploying the central-services Helm chart" if you need more information:

   $ helm upgrade -n stackrox \
       stackrox-central-services rhacs/central-services \
       --reuse-values \
       -f <path_to_values_public.yaml> \
       -f <path_to_generated-values.yaml> \
       --set scannerV4.disable=false

   where:

   <path_to_generated-values.yaml>

   Specifies the path to the generated values YAML file. When updating the system and installing a new component, you must provide the internal CA. See "Retrieving the automatically generated certificate authority".

Procedure

1. On the secured cluster, run the following command, using the instructions in "Configuring the secured-cluster-services Helm chart with customizations" if you need more information:

   $ helm upgrade -n stackrox \
       stackrox-central-services rhacs/secured-cluster-services \
       --reuse-values \
       -f <path_to_values_public.yaml> \
       -f <path_to_generated-values.yaml> \
       --set scannerV4.disable=false

   where:

   <path_to_generated-values.yaml>

   Specifies the path to the generated values YAML file. When updating the system and installing a new component, you must provide the internal CA. See "Retrieving the automatically generated certificate authority".