Support to Define the watching scope of the Operator

[thiruvikraman-subburaman]

Component(s)

collector, target allocator

Is your feature request related to a problem? Please describe.

Currently, OpenTelemetry support watching of CustomResource in the same namespace as Operator

Rationale:

An Operator should be namespace-scoped if it is intended to be flexibly deployed. This scope permits decoupled upgrades, namespace isolation for failures and monitoring, and differing API definitions.
By default, a namespace-scoped Custom Controller watches for instances of the Custom Resource, which it is responsible for, in the same K8s namespace as the Custom Controller itself is deployed in. However, some Operators are not suited for a deployment where the Operator watches for events only in the own namespace.

https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-operator/conf/crds/crd-opentelemetrycollector.yaml#L37

Describe the solution you'd like

Should possibly expose below options to watch in ownNs, multiNs and allNs

possible options:

OwnNamespace: the Custom Controller of the Operator is configured to watch for events in the namespace it is deployed in.
MultiNamespaces: the Custom Controller of the Operator is configured to watch for events in one or several namespaces (but not all), and the namespace it is deployed in could be part of that (but does not have to be).
AllNamespaces: the Custom Controller of the Operator is configured to watch for events in all namespaces.

Describe alternatives you've considered

No response

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}