openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Update OLM global namespace next steps

Browse Source
This commit is contained in:
Alex Dellapenta
2023-06-22 12:59:40 -06:00
parent 03189817d8
commit bbab257960
5 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

0
logging/v5_5/attributes → logging/v5_5/_attributes
View File

0
logging/v5_6/attributes → logging/v5_6/_attributes
View File

0
logging/v5_7/attributes → logging/v5_7/_attributes
View File

6
modules/olm-installing-from-operatorhub-using-cli.adoc
View File

@@ -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::[]

3
operators/admin/olm-adding-operators-to-cluster.adoc
View File

@@ -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]
====