Merge pull request #58857 from stevsmit/4639-412

Renames variants of the OpenShift internal image registry to OpenShif…

Author: stevsmit

_attributes/attributes-microshift.adoc

@@ -4,8 +4,9 @@
 :experimental:
 :imagesdir: images
 :OCP: OpenShift Container Platform
-:ocp-version: 4.12
-:rhel-major: rhel-8
+:ocp-version: 4.13
+:product-registry: OpenShift image registry
+:rhel-major: rhel-9
 :op-system-base-full: Red Hat Enterprise Linux (RHEL)
 :op-system: RHEL
 :op-system-ostree-first: Red Hat Enterprise Linux (RHEL) for Edge

_attributes/attributes-openshift-dedicated.adoc

@@ -14,6 +14,7 @@
 :hybrid-console-second: Hybrid Cloud Console
 :AWS: Amazon Web Services (AWS)
 :GCP: Google Cloud Platform (GCP)
+:product-registry: OpenShift image registry
 :kebab: image:kebab.png[title="Options menu"]
 :rhq-short: Red Hat Quay
 :SMProductName: Red Hat OpenShift Service Mesh

_attributes/common-attributes.adoc

@@ -42,6 +42,7 @@ endif::openshift-origin[]
 :insights-advisor-url: link:https://console.redhat.com/openshift/insights/advisor/[Insights Advisor]
 :hybrid-console: Red Hat Hybrid Cloud Console
 :hybrid-console-second: Hybrid Cloud Console
+:product-registry: OpenShift image registry
 :rh-storage-first: Red Hat OpenShift Data Foundation
 :rh-storage: OpenShift Data Foundation
 :rh-rhacm-first: Red Hat Advanced Cluster Management (RHACM)

_unused_topics/images-s2i-nodejs-pulling-images.adoc

@@ -46,5 +46,5 @@ $ podman pull openshift/nodejs-010-centos7
 ----
 ////
 
-To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-title} image registry. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
+To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-registry}. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
 image stream.

_unused_topics/images-using-images-s2i-perl-pulling-images.adoc

@@ -46,5 +46,5 @@ $ podman pull openshift/perl-516-centos7
 ----
 ////
 
-To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-title} image registry. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
+To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-registry}. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
 image stream.

_unused_topics/images-using-images-s2i-php-pulling-images.adoc

@@ -51,5 +51,5 @@ $ podman pull openshift/php-56-centos7
 ----
 ////
 
-To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-title} image registry. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
+To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-registry}. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
 image stream.

_unused_topics/images-using-images-s2i-python-pulling-images.adoc

@@ -71,5 +71,5 @@ $ podman pull centos/python-35-centos7
 ----
 ////
 
-To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-title} image registry. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
+To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-registry}. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
 image stream.

_unused_topics/images-using-images-s2i-ruby-pulling-images.adoc

@@ -65,5 +65,5 @@ $ podman pull centos/ruby-23-centos7
 ----
 ////
 
-To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-title} image registry. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
+To use these images, you can either access them directly from registry.redhat.io, or push them into your {product-registry}. Additionally, you can create an image stream that points to the image, either in your container image registry or at the external location. Your {product-title} resources can then reference the
 image stream.

cli_reference/developer_cli_odo/using_odo_in_a_restricted_environment/creating-and-deploying-a-component-to-the-disconnected-cluster.adoc

@@ -12,7 +12,7 @@ After you push the `init` image to a cluster with a mirrored registry, you must
 
 * Install `oc` on the client operating system.
 * xref:../../../cli_reference/developer_cli_odo/installing-odo.adoc#installing-odo-on-linux_installing-odo[Install `{odo-title}`] on the client operating system.
-* Access to an restricted cluster with a configured internal registry or a mirror registry.
+* Access to an restricted cluster with a configured {product-registry} or a mirror registry.
 * xref:../../../cli_reference/developer_cli_odo/using_odo_in_a_restricted_environment/pushing-the-odo-init-image-to-the-restricted-cluster-registry.adoc#pushing-the-odo-init-image-to-a-mirror-registry_pushing-the-odo-init-image-to-the-restricted-cluster-registry[Push the `odo` init image to your cluster registry].
 
 include::modules/developer-cli-odo-mirroring-a-supported-builder-image.adoc[leveloffset=+1]

cli_reference/developer_cli_odo/using_odo_in_a_restricted_environment/pushing-the-odo-init-image-to-the-restricted-cluster-registry.adoc

@@ -6,13 +6,13 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Depending on the configuration of your cluster and your operating system you can either push the `odo` init image to a mirror registry or directly to an internal registry.
+Depending on the configuration of your cluster and your operating system you can either push the `odo` init image to a mirror registry or directly to an {product-registry}.
 
 == Prerequisites
 
 * Install `oc` on the client operating system.
 * xref:../../../cli_reference/developer_cli_odo/installing-odo.adoc#installing-odo-on-linux_installing-odo[Install `{odo-title}`] on the client operating system.
-* Access to a restricted cluster with a configured internal registry or a mirror registry.
+* Access to a restricted cluster with a configured {product-registry} or a mirror registry.
 
 include::modules/developer-cli-odo-pushing-the-odo-init-image-to-a-mirror-registry.adoc[leveloffset=+1]
 include::modules/developer-cli-odo-pushing-the-odo-init-image-to-an-internal-registry-directly.adoc[leveloffset=+1]