Multiple namespace installation isn't the default behaviour and is not documented #492
Description
Hi,
we are using the helm-operator-plugins in the RHTPA Operator.
During a multiple installation with two operators in different namespace with no clusterroles and only roles used, we found that the second operator start to receive events from the first namespace where was started the first operator with its deployment, bypassing the installMode single namespace installMode and the roles.
The solution https://github.com/trustification/trusted-profile-analyzer-operator/pull/319/files is to add the WATCH_NAMESPACE env plus the set of a fresh cacheOpts, but I'm wondering why isn't explained in the docs the default behaviour of the operator is to be installed in a single namespace and observe all namespaced where the product instance (i.e. RHTPA in our case) is deployed.
Worth to open a PR to add in the readme this changes in case of multiple namespace installatins is required.