Merge pull request #35692 from vikram-redhat/cloud.redhat.com

changed cloud.redhat.com to console.redhat.com

Author: vikram-redhat

cicd/pipelines/installing-pipelines.adoc

@@ -18,7 +18,7 @@ This guide walks cluster administrators through the process of installing the {p
 * You have installed xref:../../cli_reference/tkn_cli/installing-tkn.adoc#installing-tkn[OpenShift Pipelines (`tkn`) CLI] on your local system.
 
 ifdef::openshift-origin[]
-* Ensure that you have downloaded the link:https://cloud.redhat.com/openshift/install/pull-secret[pull secret from the Red Hat OpenShift Cluster Manager site] as shown in the xref:../../installing/installing_gcp/installing-gcp-customizations.adoc#installation-obtaining-installer_installing-gcp-customizations[Obtaining the installation program] to install this Operator.
+* Ensure that you have downloaded the link:https://console.redhat.com/openshift/install/pull-secret[pull secret from the Red Hat OpenShift Cluster Manager site] as shown in the xref:../../installing/installing_gcp/installing-gcp-customizations.adoc#installation-obtaining-installer_installing-gcp-customizations[Obtaining the installation program] to install this Operator.
 +
 If you have the pull secret, add the `redhat-operators` catalog to the OperatorHub custom resource (CR) as shown in xref:../../post_installation_configuration/preparing-for-users.adoc#olm-installing-operators-from-operatorhub-configure_post-install-preparing-for-users[Configuring {product-title} to use Red Hat Operators].
 endif::[]

getting_started/deleting-your-cluster.adoc

@@ -5,7 +5,7 @@ include::modules/common-attributes.adoc[]
 
 To delete your {product-title} cluster:
 
-. From link:https://cloud.redhat.com/openshift[cloud.redhat.com/openshift], click
+. From link:https://console.redhat.com/openshift[console.redhat.com/openshift], click
  on the cluster you want to delete.
 
 . Click the *Actions* button, then *Delete Cluster*.

modules/cluster-entitlements.adoc

@@ -123,7 +123,7 @@ your cluster.
 
 You must have internet access to:
 
-* Access the link:https://cloud.redhat.com/openshift[{cloud-redhat-com}] page to download the installation program and perform subscription management. If the cluster has internet access and you do not disable Telemetry, that service automatically entitles your cluster.
+* Access the link:https://console.redhat.com/openshift[{cloud-redhat-com}] page to download the installation program and perform subscription management. If the cluster has internet access and you do not disable Telemetry, that service automatically entitles your cluster.
 * Access link:http://quay.io[Quay.io] to obtain the packages that are required to install your cluster.
 * Obtain the packages that are required to perform cluster updates.
 ifdef::openshift-enterprise,openshift-webscale[]

modules/cluster-logging-deploy-cli.adoc

@@ -20,7 +20,7 @@ If you use a local volume for persistent storage, do not use a raw block volume,
 Elasticsearch is a memory-intensive application. By default, {product-title} installs three Elasticsearch nodes with memory requests and limits of 16 GB. This initial set of three {product-title} nodes might not have enough memory to run Elasticsearch within your cluster. If you experience memory issues that are related to Elasticsearch, add more Elasticsearch nodes to your cluster rather than increasing the memory on existing nodes.
 
 ifdef::openshift-origin[]
-* Ensure that you have downloaded the link:https://cloud.redhat.com/openshift/install/pull-secret[pull secret from the Red Hat OpenShift Cluster Manager site] as shown in _Obtaining the installation program_ in the installation documentation for your platform.
+* Ensure that you have downloaded the link:https://console.redhat.com/openshift/install/pull-secret[pull secret from the Red Hat OpenShift Cluster Manager site] as shown in _Obtaining the installation program_ in the installation documentation for your platform.
 +
 If you have the pull secret, add the `redhat-operators` catalog to the OperatorHub custom resource (CR) as shown in *Configuring {product-title} to use Red Hat Operators*.
 endif::[]

modules/cluster-logging-deploy-console.adoc

@@ -25,7 +25,7 @@ If you use a local volume for persistent storage, do not use a raw block volume,
 Elasticsearch is a memory-intensive application. By default, {product-title} installs three Elasticsearch nodes with memory requests and limits of 16 GB. This initial set of three {product-title} nodes might not have enough memory to run Elasticsearch within your cluster. If you experience memory issues that are related to Elasticsearch, add more Elasticsearch nodes to your cluster rather than increasing the memory on existing nodes.
 
 ifdef::openshift-origin[]
-* Ensure that you have downloaded the link:https://cloud.redhat.com/openshift/install/pull-secret[pull secret from the Red Hat OpenShift Cluster Manager site] as shown in _Obtaining the installation program_ in the installation documentation for your platform.
+* Ensure that you have downloaded the link:https://console.redhat.com/openshift/install/pull-secret[pull secret from the Red Hat OpenShift Cluster Manager site] as shown in _Obtaining the installation program_ in the installation documentation for your platform.
 +
 If you have the pull secret, add the `redhat-operators` catalog to the OperatorHub custom resource (CR) as shown in _Configuring {product-title} to use Red Hat Operators_.
 endif::[]

modules/cluster-telemetry.adoc

@@ -67,7 +67,7 @@
 ifndef::openshift-origin[]
 = Telemetry access for {product-title}
 
-In {product-title} {product-version}, the Telemetry service, which runs by default to provide metrics about cluster health and the success of updates, requires internet access. If your cluster is connected to the internet, Telemetry runs automatically, and your cluster is registered to the link:https://cloud.redhat.com/openshift[{cloud-redhat-com} (OCM)].
+In {product-title} {product-version}, the Telemetry service, which runs by default to provide metrics about cluster health and the success of updates, requires internet access. If your cluster is connected to the internet, Telemetry runs automatically, and your cluster is registered to the link:https://console.redhat.com/openshift[{cloud-redhat-com} (OCM)].
 
 After you confirm that your {cloud-redhat-com} inventory is correct, either maintained automatically by Telemetry or manually by using OCM, link:https://access.redhat.com/documentation/en-us/subscription_central/2020-04/html/getting_started_with_subscription_watch/con-how-to-select-datacollection-tool_assembly-requirements-and-your-responsibilities-ctxt#red_hat_openshift[use subscription watch] to track your {product-title} subscriptions at the account or multi-cluster level.
 

modules/configuring-firewall.adoc

@@ -31,7 +31,7 @@ There are no special configuration considerations for services running on only c
 
 |`sso.redhat.com`
 |443, 80
-|The `https://cloud.redhat.com/openshift` site uses authentication from `sso.redhat.com`
+|The `https://console.redhat.com/openshift` site uses authentication from `sso.redhat.com`
 
 |`openshift.org`
 |443, 80
@@ -63,7 +63,7 @@ CDN host names, such as `cdn01.quay.io`, are covered when you add a wildcard ent
 |443, 80
 |Required for Telemetry
 
-|`https://cloud.redhat.com/api/ingress`
+|`https://console.redhat.com/api/ingress`
 |443, 80
 |Required for Telemetry and for `insights-operator`
 |===
@@ -129,7 +129,7 @@ CDN host names, such as `cdn01.quay.io`, are covered when you add a wildcard ent
 |443, 80
 |Required to download {op-system-first} images.
 
-|`cloud.redhat.com/openshift`
+|`console.redhat.com/openshift`
 |443, 80
 |Required for your cluster token.
 

modules/dedicated-creating-your-cluster.adoc

@@ -7,7 +7,7 @@
 
 To create your {product-title} cluster:
 
-. Log in to link:https://cloud.redhat.com/openshift[cloud.redhat.com/openshift].
+. Log in to link:https://console.redhat.com/openshift[console.redhat.com/openshift].
 
 . Select *Create Cluster* -> *Red Hat OpenShift Dedicated*.
 
@@ -38,7 +38,7 @@ indicator. This will indicate that your cluster is *Ready* for use.
 
 To access your {product-title} cluster:
 
-. From link:https://cloud.redhat.com/openshift[cloud.redhat.com/openshift], click
+. From link:https://console.redhat.com/openshift[console.redhat.com/openshift], click
  on the cluster you want to access.
 
  . Click *Launch Console*.

modules/dedicated-managing-dedicated-administrators.adoc

@@ -7,7 +7,7 @@
 
 Administrator roles are managed using a `dedicated-admins` group on the cluster.
 Existing members of this group can edit membership via the
-link:https://cloud.redhat.com/openshift[{cloud-redhat-com}] site.
+link:https://console.redhat.com/openshift[{cloud-redhat-com}] site.
 
 [id="dedicated-administrators-adding-user_{context}"]
 == Adding a user

modules/dedicated-scaling-your-cluster.adoc

@@ -7,7 +7,7 @@
 
 To scale your {product-title} cluster:
 
-. From link:https://cloud.redhat.com/openshift[cloud.redhat.com/openshift], click
+. From link:https://console.redhat.com/openshift[console.redhat.com/openshift], click
  on the cluster you want to resize.
 
 . Click the *Actions* button, then *Scale Cluster*.