Merge pull request #61619 from adellape/global_cli

Author: adellape

contributing_to_docs/doc_guidelines.adoc

@@ -227,7 +227,7 @@ For example, if you are creating the links in a directory that is two levels dee
 $ ln -s ../../images/ images
 $ ln -s ../../modules/ modules
 $ ln -s ../../snippets/ snippets
-$ ln -s ../../_attributes/ attributes
+$ ln -s ../../_attributes/ _attributes
 ----
 +
 Be sure to adjust the number of levels to back up (`../`) depending on how deep your directory is.

logging/v5_5/attributes renamed to logging/v5_5/_attributes

@@ -142,7 +142,7 @@ spec:
     nodeSelector: <12>
       foo: bar
 ----
-<1> For `AllNamespaces` install mode usage, specify the `openshift-operators` namespace. Otherwise, specify the relevant single namespace for `SingleNamespace` install mode usage.
+<1> For default `AllNamespaces` install mode usage, specify the `openshift-operators` namespace. Alternatively, you can specify a custom global namespace, if you have created one. Otherwise, specify the relevant single namespace for `SingleNamespace` install mode usage.
 <2> Name of the channel to subscribe to.
 <3> Name of the Operator to subscribe to.
 <4> Name of the catalog source that provides the Operator.
@@ -163,3 +163,7 @@ $ oc apply -f sub.yaml
 ----
 +
 At this point, OLM is now aware of the selected Operator. A cluster service version (CSV) for the Operator should appear in the target namespace, and APIs provided by the Operator should be available for creation.
+
+ifeval::["{context}" == "olm-installing-operators-in-namespace"]
+:!olm-user:
+endif::[]

logging/v5_6/attributes renamed to logging/v5_6/_attributes

@@ -41,6 +41,7 @@ include::modules/olm-installing-from-operatorhub-using-cli.adoc[leveloffset=+1]
 * xref:../../operators/understanding/olm/olm-understanding-operatorgroups.adoc#olm-operatorgroups-about_olm-understanding-operatorgroups[About Operator groups]
 
 include::modules/olm-installing-specific-version-cli.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 
@@ -65,7 +66,7 @@ After completing the Operator installation, the Operator resides in the tenant O
 include::modules/olm-installing-global-namespaces.adoc[leveloffset=+1]
 .Next steps
 
-* Install the desired Operator in the installation namespace. This task is more easily performed by using the OperatorHub in the web console instead of the CLI; for a detailed procedure, see xref:../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-installing-from-operatorhub-using-web-console_olm-adding-operators-to-a-cluster[Installing from OperatorHub using the web console].
+* Install the desired Operator in your custom global namespace. Because the web console does not populate the *Installed Namespace* menu during Operator installation with custom global namespaces, this task can only be performed with the OpenShift CLI (`oc`). For a detailed procedure, see xref:../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-installing-operator-from-operatorhub-using-cli_olm-adding-operators-to-a-cluster[Installing from OperatorHub using the CLI].
 +
 [NOTE]
 ====