Merge pull request #20268 from adellape/link_operatorgroups

Add info/link re OperatorGroups

Author: adellape

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

@@ -46,7 +46,11 @@ Channels:
 $ oc describe packagemanifests <operator_name> -n openshift-marketplace
 ----
 
-. The namespace to which you subscribe the Operator must have an OperatorGroup
+. An OperatorGroup is an OLM resource that selects target namespaces in which to
+generate required RBAC access for all Operators in the same namespace as the
+OperatorGroup.
++
+The namespace to which you subscribe the Operator must have an OperatorGroup
 that matches the Operator's InstallMode, either the `AllNamespaces` or
 `SingleNamespace` mode. If the Operator you intend to install uses the
 `AllNamespaces`, then the `openshift-operators` namespace already has an
@@ -117,11 +121,3 @@ $ oc apply -f sub.yaml
 At this point, the OLM is now aware of the selected Operator. A
 ClusterServiceVersion (CSV) for the Operator should appear in the target
 namespace, and APIs provided by the Operator should be available for creation.
-
-.Additional resources
-
-* To install custom Operators to a cluster using the OperatorHub, you must first
-upload your Operator artifacts to Quay.io, then add your own `OperatorSource` to
-your cluster. Optionally, you can add Secrets to your Operator to provide
-authentication. After, you can manage the Operator in your cluster as you would
-any other Operator. For these steps, see link:https://github.com/operator-framework/community-operators/blob/master/docs/testing-operators.md[Testing Operators].

modules/olm-operatorgroups-about.adoc

@@ -6,8 +6,8 @@
 = About OperatorGroups
 
 An _OperatorGroup_ is an OLM resource that provides multitenant configuration to
-OLM-installed Operators. An OperatorGroup selects a set of target namespaces in
-which to generate required RBAC access for its member Operators.
+OLM-installed Operators. An OperatorGroup selects target namespaces in which to
+generate required RBAC access for its member Operators.
 
 The set of target namespaces is provided by a comma-delimited string stored in
 the ClusterServiceVersion's (CSV) `olm.targetNamespaces` annotation. This

operators/olm-adding-operators-to-cluster.adoc

@@ -12,4 +12,7 @@ include::modules/olm-installing-operators-from-operatorhub.adoc[leveloffset=+1]
 include::modules/olm-installing-from-operatorhub-using-web-console.adoc[leveloffset=+2]
 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
 include::modules/olm-installing-from-operatorhub-using-cli.adoc[leveloffset=+2]
+.Additional resources
+
+* xref:../operators/understanding_olm/olm-understanding-operatorgroups.adoc#olm-operatorgroups-about_olm-understanding-operatorgroups[About OperatorGroups]
 endif::[]