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

OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs

Browse Source
This commit is contained in:
dfitzmau
2025-03-05 12:55:46 +00:00
committed by openshift-cherrypick-robot
parent 71c4bbe175
commit bd5f75cc12
7 changed files with 99 additions and 279 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -38,6 +38,7 @@ include::modules/olm-installing-operators-from-operatorhub.adoc[leveloffset=+1]
* xref:../../operators/understanding/olm-understanding-operatorhub.adoc#olm-understanding-operatorhub[Understanding OperatorHub]
// Installing from OperatorHub by using the CLI
include::modules/olm-installing-from-operatorhub-using-web-console.adoc[leveloffset=+1]
[role="_additional-resources"]
@@ -46,6 +47,8 @@ include::modules/olm-installing-from-operatorhub-using-web-console.adoc[leveloff
* xref:../../operators/admin/olm-upgrading-operators.adoc#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending Operator update]
ifdef::openshift-enterprise,openshift-webscale,openshift-origin,openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
// Installing from OperatorHub by using the CLI
include::modules/olm-installing-from-operatorhub-using-cli.adoc[leveloffset=+1]
[role="_additional-resources"]
@@ -58,7 +61,7 @@ include::modules/olm-installing-from-operatorhub-using-cli.adoc[leveloffset=+1]
include::modules/olm-preparing-multitenant-operators.adoc[leveloffset=+1]
.Next steps
* Install the Operator in the tenant Operator 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 Operator in the tenant Operator namespace. This task is more easily performed by using the OperatorHub in the web console instead of the CLI; for a detailed procedure, "Installing from OperatorHub using the web console".
+
[NOTE]
====
@@ -71,9 +74,10 @@ After completing the Operator installation, the Operator resides in the tenant O
* xref:../../operators/understanding/olm-multitenancy.adoc#olm-multitenancy[Operators in multitenant clusters]
include::modules/olm-installing-global-namespaces.adoc[leveloffset=+1]
.Next steps
* 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].
* 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, the install task can only be performed with the OpenShift CLI (`oc`). For a detailed installation procedure, see "Installing from OperatorHub using the CLI".
+
[NOTE]
====