Merge pull request #75868 from adellape/fix_callouts_maybe

Fix callout WARNINGS in OLM-related modules

Author: adellape

modules/olm-accessing-images-private-registries.adoc

@@ -189,12 +189,15 @@ $ oc create secret generic <secret_name> \
 
 .. Verify the name of the service account for the Operator by searching the tenant namespace:
 +
+--
 [source,terminal]
 ----
 $ oc get sa -n <tenant_namespace> <1>
 ----
 <1> If the Operator was installed in an individual namespace, search that namespace. If the Operator was installed for all namespaces, search the `openshift-operators` namespace.
+--
 +
+--
 .Example output
 [source,terminal]
 ----
@@ -205,6 +208,7 @@ deployer        2         6m1s
 etcd-operator   2         5m18s <1>
 ----
 <1> Service account for an installed etcd Operator.
+--
 
 .. Link the secret to the service account for the Operator:
 +

modules/olm-creating-fb-catalog-image.adoc

@@ -34,6 +34,7 @@ $ mkdir <catalog_dir>
 
 .. Generate a Dockerfile that can build a catalog image by running the `opm generate dockerfile` command:
 +
+--
 [source,terminal,subs="attributes+"]
 ----
 ifdef::openshift-origin[]
@@ -47,9 +48,11 @@ endif::[]
 ifndef::openshift-origin[]
 <1> Specify the official Red Hat base image by using the `-i` flag, otherwise the Dockerfile uses the default upstream image.
 endif::[]
+--
 +
 The Dockerfile must be in the same parent directory as the catalog directory that you created in the previous step:
 +
+--
 .Example directory structure
 [source,terminal]
 ----
@@ -60,6 +63,7 @@ The Dockerfile must be in the same parent directory as the catalog directory tha
 <1> Parent directory
 <2> Catalog directory
 <3> Dockerfile generated by the `opm generate dockerfile` command
+--
 
 .. Populate the catalog with the package definition for your Operator by running the `opm init` command:
 +

modules/olm-mirroring-catalog-airgapped.adoc

@@ -19,6 +19,7 @@ If your mirror registry is on a completely disconnected, or airgapped, host, tak
 
 . Run the following command on your workstation with unrestricted network access to mirror the content to local files:
 +
+--
 [source,terminal]
 ----
 $ oc adm catalog mirror \
@@ -33,7 +34,9 @@ $ oc adm catalog mirror \
 <3> Optional: If required, specify the location of your registry credentials file.
 <4> Optional: If you do not want to configure trust for the target registry, add the `--insecure` flag.
 <5> Optional: Specify which platform and architecture of the index image to select when multiple variants are available. Images are specified as `'<platform>/<arch>[/<variant>]'`. This does not apply to images referenced by the index. Valid values are `linux/amd64`, `linux/ppc64le`, `linux/s390x`, `linux/arm64`, and `.*`
+--
 +
+--
 .Example output
 [source,terminal]
 ----
@@ -47,6 +50,7 @@ To upload local images to a registry, run:
 ----
 <1> Record the manifests directory name that is generated. This directory is referenced in subsequent procedures.
 <2> Record the expanded `file://` path that is based on your provided index image. This path is referenced in a subsequent step.
+--
 +
 This command creates a `v2/` directory in your current directory.
 

modules/olm-mirroring-catalog-colocated.adoc

@@ -28,6 +28,7 @@ $ podman login <mirror_registry>
 
 . Run the following command to extract and mirror the content to the mirror registry:
 +
+--
 [source,terminal]
 ----
 $ oc adm catalog mirror \
@@ -45,7 +46,9 @@ $ oc adm catalog mirror \
 <4> Optional: If you do not want to configure trust for the target registry, add the `--insecure` flag.
 <5> Optional: Specify which platform and architecture of the index image to select when multiple variants are available. Images are passed as `'<platform>/<arch>[/<variant>]'`. This does not apply to images referenced by the index. Valid values are `linux/amd64`, `linux/ppc64le`, `linux/s390x`, `linux/arm64`.
 <6> Optional: Generate only the manifests required for mirroring without actually mirroring the image content to a registry. This option can be useful for reviewing what will be mirrored, and lets you make any changes to the mapping list, if you require only a subset of packages. You can then use the `mapping.txt` file with the `oc image mirror` command to mirror the modified list of images in a later step. This flag is intended for only advanced selective mirroring of content from the catalog.
+--
 +
+--
 .Example output
 [source,terminal,subs="attributes+"]
 ----
@@ -62,6 +65,7 @@ wrote mirroring manifests to manifests-{index-image}-1614211642 <2>
 ====
 Red Hat Quay does not support nested repositories. As a result, running the `oc adm catalog mirror` command will fail with a `401` unauthorized error. As a workaround, you can use the `--max-components=2` option when running the `oc adm catalog mirror` command to disable the creation of nested repositories. For more information on this workaround, see the link:https://access.redhat.com/solutions/5440741[Unauthorized error thrown while using catalog mirror command with Quay registry] Knowledgebase Solution.
 ====
+--
 
 :!index-image-pullspec:
 :!index-image: