OSDOCS#9586: Replacing deprecated 'oc registry info' commands

Author: bergerhoffer

modules/configuring-private-storage-endpoint-azure-user-provided-vnet-subnet.adoc

@@ -14,7 +14,7 @@ Use the following procedure to configure a storage account that has public netwo
 * You must know the VNet and subnet names used for your Azure environment.
 * If your network was configured in a separate resource group in Azure, you must also know its name.
 
-.Procedure 
+.Procedure
 
 . Edit the Image Registry Operator `config` object and configure the private endpoint using your VNet and subnet names:
 +
@@ -40,7 +40,7 @@ spec:
 # ...
 ----
 
-. Optional: Enter the following command to confirm that the Operator has completed provisioning. This might take a few minutes. 
+. Optional: Enter the following command to confirm that the Operator has completed provisioning. This might take a few minutes.
 +
 [source,terminal]
 ----
@@ -58,14 +58,16 @@ When redirect is enabled, pulling images from outside of the cluster will not wo
 +
 [source,terminal]
 ----
-$ oc registry info --internal=true
+$ oc get imagestream -n openshift
 ----
 +
 .Example output
 +
 [source,terminal]
 ----
-image-registry.openshift-image-registry.svc:5000
+NAME   IMAGE REPOSITORY                                                 TAGS     UPDATED
+cli    image-registry.openshift-image-registry.svc:5000/openshift/cli   latest   8 hours ago
+...
 ----
 
 . Enter debug mode by running the following command:
@@ -114,4 +116,4 @@ Copying config 22667f5368 done
 Writing manifest to image destination
 Storing signatures
 22667f53682a2920948d19c7133ab1c9c3f745805c14125859d20cede07f11f9
-----
+----

modules/configuring-private-storage-endpoint-azure-vnet-subnet-iro-discovery.adoc

@@ -8,14 +8,14 @@
 
 The following procedure shows you how to set up a private storage endpoint on Azure by configuring the Image Registry Operator to discover VNet and subnet names.
 
-.Prerequisites 
+.Prerequisites
 
 * You have configured the image registry to run on Azure.
-* Your network has been set up using the Installer Provisioned Infrastructure installation method. 
+* Your network has been set up using the Installer Provisioned Infrastructure installation method.
 +
-For users with a custom network setup, see "Configuring a private storage endpoint on Azure with user-provided VNet and subnet names". 
+For users with a custom network setup, see "Configuring a private storage endpoint on Azure with user-provided VNet and subnet names".
 
-.Procedure 
+.Procedure
 
 . Edit the Image Registry Operator `config` object and set `networkAccess.type` to `Internal`:
 +
@@ -37,7 +37,7 @@ spec:
 # ...
 ----
 
-. Optional: Enter the following command to confirm that the Operator has completed provisioning. This might take a few minutes. 
+. Optional: Enter the following command to confirm that the Operator has completed provisioning. This might take a few minutes.
 +
 [source,terminal]
 ----
@@ -62,14 +62,16 @@ When redirect is enabled,  pulling images from outside of the cluster will not w
 +
 [source,terminal]
 ----
-$ oc registry info --internal=true
+$ oc get imagestream -n openshift
 ----
 +
 .Example output
 +
 [source,terminal]
 ----
-image-registry.openshift-image-registry.svc:5000
+NAME   IMAGE REPOSITORY                                                 TAGS     UPDATED
+cli    image-registry.openshift-image-registry.svc:5000/openshift/cli   latest   8 hours ago
+...
 ----
 
 . Enter debug mode by running the following command:

modules/disabling-redirect-private-storage-endpoint-azure.adoc

@@ -6,9 +6,9 @@
 [id="disabling-redirect-private-storage-endpoint-azure_{context}"]
 = Optional: Disabling redirect when using a private storage endpoint on Azure
 
-By default, redirect is enabled when using the image registry. Redirect allows off-loading of traffic from the registry pods into the object storage, which makes pull faster. When redirect is enabled and the storage account is private, users from outside of the cluster are unable to pull images from the registry. 
+By default, redirect is enabled when using the image registry. Redirect allows off-loading of traffic from the registry pods into the object storage, which makes pull faster. When redirect is enabled and the storage account is private, users from outside of the cluster are unable to pull images from the registry.
 
-In some cases, users might want to disable redirect so that users from outside of the cluster can pull images from the registry. 
+In some cases, users might want to disable redirect so that users from outside of the cluster can pull images from the registry.
 
 Use the following procedure to disable redirect.
 
@@ -19,7 +19,7 @@ Use the following procedure to disable redirect.
 
 .Procedure
 
-* Enter the following command to disable redirect on the image 
+* Enter the following command to disable redirect on the image
 registry configuration:
 +
 [source,terminal]
@@ -33,14 +33,16 @@ $ oc patch configs.imageregistry cluster --type=merge -p '{"spec":{"disableRedir
 +
 [source,terminal]
 ----
-$ oc registry info
+$ oc get imagestream -n openshift
 ----
 +
 .Example output
 +
 [source,terminal]
 ----
-default-route-openshift-image-registry.<cluster_dns>
+NAME   IMAGE REPOSITORY                                           TAGS     UPDATED
+cli    default-route-openshift-image-registry.<cluster_dns>/cli   latest   8 hours ago
+...
 ----
 
 . Enter the following command to log in to your container registry:
@@ -76,4 +78,4 @@ Copying config 22667f5368 done
 Writing manifest to image destination
 Storing signatures
 22667f53682a2920948d19c7133ab1c9c3f745805c14125859d20cede07f11f9
-----
+----