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-49969-touch-up

Browse Source
This commit is contained in:
dfitzmau
2025-04-16 11:09:32 +01:00
committed by openshift-cherrypick-robot
parent 5ebe984d19
commit f58b809c9b
3 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/multi-arch-installing-using-cli.adoc
View File

@@ -76,7 +76,7 @@ $ oc create -f <file_name> <1>
[NOTE]
====
For more details about configuring the `Subscription` object and `OperatorGroup` object, see "Installing from OperatorHub using the CLI".
For more details about configuring the `Subscription` object and `OperatorGroup` object, see "Installing from OperatorHub by using the CLI".
====
.Verification

10
modules/nw-metalLB-basic-upgrade-operator.adoc
View File

@@ -66,8 +66,8 @@ $ oc -n metallb-system get installplan
.Example output that shows install-tsz2g as a manual install plan
[source,terminal,subs="attributes+"]
----
NAME CSV APPROVAL APPROVED
install-shpmd metallb-operator.v4.18.0-202502261233 Automatic true
NAME CSV APPROVAL APPROVED
install-shpmd metallb-operator.v{product-version}.0-202502261233 Automatic true
install-tsz2g metallb-operator.v{product-version}.0-202503102139 Manual false
----
@@ -95,8 +95,8 @@ $ oc -n metallb-system get csv
----
+
.Example output
[source,terminal]
[source,terminal,subs="attributes+"]
----
NAME DISPLAY VERSION REPLACE PHASE
metallb-operator.v4.19.0-202503102139 MetalLB Operator {product-version}.0-202503102139 metallb-operator.v4.18.0-202502261233 Succeeded
NAME DISPLAY VERSION REPLACE PHASE
metallb-operator.v<latest>.0-202503102139 MetalLB Operator {product-version}.0-202503102139 metallb-operator.v{product-version}.0-202502261233 Succeeded
----

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

@@ -77,7 +77,7 @@ 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, the install task can only be performed with the OpenShift CLI (`oc`). For a detailed installation procedure, see "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 by using the CLI".
+
[NOTE]
====