Skip to content

Commit bb37ad1

Browse files
Merge pull request #74660 from michaelryanpeter/ocpbugs-32056-clarify-global-operators-operator-group
OCPBUGS#32056: Clarify the `global-operators` Operator group exists
2 parents 37132b2 + ae1a235 commit bb37ad1

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

modules/olm-installing-from-operatorhub-using-cli.adoc

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -73,13 +73,14 @@ $ oc describe packagemanifests <operator_name> -n openshift-marketplace
7373

7474
. An Operator group, defined by an `OperatorGroup` object, selects target namespaces in which to generate required RBAC access for all Operators in the same namespace as the Operator group.
7575
+
76-
The namespace to which you subscribe the Operator must have an Operator group that matches the install mode of the Operator, either the `AllNamespaces` or `SingleNamespace` mode. If the Operator you intend to install uses the `AllNamespaces`, then the `openshift-operators` namespace already has an appropriate Operator group in place.
76+
The namespace to which you subscribe the Operator must have an Operator group that matches the install mode of the Operator, either the `AllNamespaces` or `SingleNamespace` mode. If the Operator you intend to install uses the `AllNamespaces` mode, the `openshift-operators` namespace already has the appropriate `global-operators` Operator group in place.
7777
+
7878
However, if the Operator uses the `SingleNamespace` mode and you do not already have an appropriate Operator group in place, you must create one.
7979
+
8080
[NOTE]
8181
====
82-
The web console version of this procedure handles the creation of the `OperatorGroup` and `Subscription` objects automatically behind the scenes for you when choosing `SingleNamespace` mode.
82+
* The web console version of this procedure handles the creation of the `OperatorGroup` and `Subscription` objects automatically behind the scenes for you when choosing `SingleNamespace` mode.
83+
* You can only have one Operator group per namespace. For more information, see "Operator groups".
8384
====
8485
8586
.. Create an `OperatorGroup` object YAML file, for example `operatorgroup.yaml`:
@@ -220,4 +221,4 @@ At this point, OLM is now aware of the selected Operator. A cluster service vers
220221

221222
ifeval::["{context}" == "olm-installing-operators-in-namespace"]
222223
:!olm-user:
223-
endif::[]
224+
endif::[]

0 commit comments

Comments
 (0)