There is no information on on what is the difference weather the operator should be installed for all namespaces or in a separate namespace. I find that in both the operand allows to:
Specify where the instances are deployed (spec.namespace parameter)
Which CIS namespaces will be able to watch
Some guidelines should be provided to clarify the namespace usage for the operator, and where the CIS is installed.
There are no general guidelines on how to setup the operand.
The following section applies when deploying an operand, not the operator IMHO
Before you install CIS using Operators on OpenShift, you must create BIG-IP login credentials to use with Operator Helm Charts:
Title
Improve OpenShift operator documentation
Description
At present:
There is no information on on what is the difference weather the operator should be installed for all namespaces or in a separate namespace. I find that in both the operand allows to:
Some guidelines should be provided to clarify the namespace usage for the operator, and where the CIS is installed.
There are no general guidelines on how to setup the operand.
The following section applies when deploying an operand, not the operator IMHO
oc create secret generic -n kube-system
--from-literal=username= --from-literal=password=