Merge pull request #30802 from adellape/macwin_catalogbuild

Add Win/Mac disclaimer for oc adm catalog build usage

Author: adellape

modules/olm-building-operator-catalog-image.adoc

@@ -16,10 +16,15 @@ Cluster administrators can build a custom Operator catalog image based on the Pa
 
 For this example, the procedure assumes use of a mirror registry that has access to both your network and the Internet.
 
+[NOTE]
+====
+Only the Linux version of the `oc` client can be used for this procedure, because the Windows and macOS versions do not provide the `oc adm catalog build` command. 
+====
+
 .Prerequisites
 
 * Workstation with unrestricted network access
-* `oc` version 4.3.5+
+* `oc` version 4.3.5+ Linux client
 * `podman` version 1.9.3+
 * Access to mirror registry that supports link:https://docs.docker.com/registry/spec/manifest-v2-2/[Docker v2-2]
 * If you are working with private registries, set the `REG_CREDS` environment variable to the file path of your registry credentials for use in later steps. For example, for the `podman` CLI:

modules/olm-updating-operator-catalog-image.adoc

@@ -16,10 +16,15 @@ After a cluster administrator has configured OperatorHub to use custom Operator
 
 For this example, the procedure assumes a custom `redhat-operators` catalog image is already configured for use with OperatorHub.
 
+[NOTE]
+====
+Only the Linux version of the `oc` client can be used for this procedure, because the Windows and macOS versions do not provide the `oc adm catalog build` command.
+====
+
 .Prerequisites
 
 * Workstation with unrestricted network access
-* `oc` version 4.3.5+
+* `oc` version 4.3.5+ Linux client
 * `podman` version 1.9.3+
 * Access to mirror registry that supports link:https://docs.docker.com/registry/spec/manifest-v2-2/[Docker v2-2]
 * OperatorHub configured to use custom catalog images