anchor.diff:  [id="olm-operatorgroups-target-namespace_{context}"]
   = Target namespace selection
   
  -The set of namespaces for the OperatorGroup is specified using a label selector
  -with the `spec.selector` field:
  -
  -[source,yaml]
  -----
  -apiVersion: operators.coreos.com/v1
  -kind: OperatorGroup
  -metadata:
  -  name: my-group
  -  namespace: my-namespace
  -  spec:
  -    selector:
  -      matchLabels:
  -        cool.io/prod: "true"
  -----
  -
  -You can also explicitly name the target namespaces using the
  -`spec.targetNamespaces` field:
  +You can explicitly name the target namespace for an OperatorGroup using the
  +`spec.targetNamespaces` parameter:
   
   [source,yaml]
   ----
  
positive.code: ----
  
  The resolved set of selected namespaces is shown in an OperatorGroup's
  `status.namespaces` field. A global OperatorGroup's `status.namespace` contains
  the empty string (`""`), which signals to a consuming Operator that it should
  watch all namespaces.
  
negative.code: spec:
    targetNamespaces:
    - my-namespace
  ----
  
  You can alternatively specify a namespace using a label selector with the
  `spec.selector` parameter:
  
  [source,yaml]
  ----
  apiVersion: operators.coreos.com/v1
  kind: OperatorGroup
  metadata:
    name: my-group
    namespace: my-namespace
    spec:
      selector:
        cool.io/prod: "true"
  ----
  
  [IMPORTANT]
  ====
  Listing multiple namespaces via `spec.targetNamespaces` or use of a label
  selector via `spec.selector` is not recommended, as the support for more than
  one target namespace in an OperatorGroup will likely be removed in a future
  release.
  ====
  
  If both `spec.targetNamespaces` and `spec.selector` are defined, `spec.selector`
  is ignored. Alternatively, you can omit both `spec.selector` and
  `spec.targetNamespaces` to specify a _global_ OperatorGroup, which selects all
  namespaces:
  
  [source,yaml]
  ----
  