Business Problem:

A customer that wants to run RHACS on Infrastructure Nodes needs to know how to configure the Operator (not just the Operands) to run on Infrastructure Nodes.

For customers that run "hub" clusters that are primarily composed of "Infra" nodes designated to run Advanced Cluster Security, Advanced Cluster Management and Quay, it is critical to also support running the actual Operators on Infra nodes.

Use Cases:

The current RHACS documentation does a good job detailing how to run RHACS itself on Infra nodes, but there is no documentation on how to configure the Operator itself to run on Infrastructure nodes.

Customers who also deploy Advanced Cluster Management to their hub cluster have also deployed the ACM operator on Infra nodes with well documented configuration.  This configuration should also be part of the ACS documentation.

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html-single/install/index#infra-olm-sub-add-config

Key Functionality:

Document the changes required to the "Subscription" yaml in order to run the ACS operator on Infra nodes.

Benefits:

Customers who expect to run ACS on Infra nodes will also have a properly documented solution for running the ACS Operator on Infra nodes.

Acceptance criteria:

ACS Operator pods will be scheduled on Infrastructure nodes.

Implementation Suggestions (optional):

Use the same documented solution that RHACM currently uses.  This simply requires adding "nodeSelector" and "tolerations" configuration to the RHACS "Subscription".
https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html-single/install/index#infra-olm-sub-add-config

I have tested this same configuration on the RHACS operator subscription and it works as expected (the Operator pods are now scheduled on Infra nodes).

The Subscription that I used in my cluster to schedule the operator on infra nodes:

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  labels:
    operators.coreos.com/rhacs-operator.rhacs-operator: ''
  name: rhacs-operator
  namespace: rhacs-operator
spec:
  channel: stable
  config:
    nodeSelector:
      node-role.kubernetes.io/infra: ''
    tolerations:
      - effect: NoSchedule
        key: node-role.kubernetes.io/infra
        operator: Exists
  installPlanApproval: Automatic
  name: rhacs-operator
  source: redhat-operators
  sourceNamespace: openshift-marketplace

Timeline:

Since this would seem to be a documentation issue, it would be beneficial to have the docs updated as soon as possible.