Merge pull request #88395 from stevsmit/50509-ocpbugs

Adds an extraction command to exposing the registry

Author: stevsmit

modules/registry-exposing-default-registry-manually.adoc

@@ -17,35 +17,42 @@ You can expose the route by using the `defaultRoute` parameter in the `configs.i
 
 To expose the registry using the `defaultRoute`:
 
-. Set `defaultRoute` to `true`:
+. Set `defaultRoute` to `true` by running the following command:
 +
 [source,terminal]
 ----
 $ oc patch configs.imageregistry.operator.openshift.io/cluster --patch '{"spec":{"defaultRoute":true}}' --type=merge
 ----
 +
-. Get the default registry route:
+. Get the default registry route by running the following command:
 +
 [source,terminal]
 ----
 $ HOST=$(oc get route default-route -n openshift-image-registry --template='{{ .spec.host }}')
 ----
 
-. Get the certificate of the Ingress Operator:
+. Get the certificate of the Ingress Operator by running the following command:
 +
 [source,terminal]
 ----
 $ oc extract secret/$(oc get ingresscontroller -n openshift-ingress-operator default -o json | jq '.spec.defaultCertificate.name // "router-certs-default"' -r) -n openshift-ingress --confirm
 ----
 
-. Enable the cluster's default certificate to trust the route using the following commands:
+. Move the extracted certificate to the system's trusted CA directory by running the following command:
++
+[source,terminal]
+----
+$ sudo mv tls.crt /etc/pki/ca-trust/source/anchors/
+----
+
+. Enable the cluster's default certificate to trust the route by running the following command:
 +
 [source,terminal]
 ----
 $ sudo update-ca-trust enable
 ----
 
-. Log in with podman using the default route:
+. Log in with podman using the default route by running the following command:
 +
 [source,terminal]
 ----