Merge pull request #94986 from jneczypor/OSDOCS-14988

OSDOCS-14988: Read Through of "Web Console" book for HCP migration

Author: EricPonvelle

_topic_maps/_topic_map_rosa_hcp.yml

@@ -208,7 +208,7 @@ Topics:
   File: web-console-overview
 - Name: Accessing the web console
   File: web-console
-- Name: Viewing cluster information
+- Name: Using the OpenShift Container Platform dashboard to get cluster information
   File: using-dashboard-to-get-cluster-information
 - Name: Adding user preferences
   File: adding-user-preferences
@@ -222,6 +222,8 @@ Topics:
     File: dynamic-plugins-get-started
   - Name: Deploy your plugin on a cluster
     File: deploy-plugin-cluster
+  - Name: Content Security Policy
+    File: content-security-policy
   - Name: Dynamic plugin example
     File: dynamic-plugin-example
   - Name: Dynamic plugin reference
@@ -241,6 +243,9 @@ Topics:
 - Name: About quick start tutorials
   File: creating-quick-start-tutorials
   Distros: openshift-rosa-hcp
+- Name: Optional capabilities and products
+  File: capabilities_products-web-console
+  Distros: openshift-rosa-hcp
 ---
 Name: CLI tools
 Dir: cli_reference

modules/about-administrator_web-console.adoc

@@ -8,7 +8,12 @@
 
 The cluster administrator role enables you to view the cluster inventory, capacity, general and specific utilization information, and the stream of important events, all of which help you to simplify planning and troubleshooting tasks. Both project administrators and cluster administrators can use all features in the web console.
 
+ifndef::openshift-rosa-hcp[]
 Cluster administrators can also open an embedded command-line terminal instance with the web terminal Operator in {product-title} 4.7 and later.
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa-hcp[]
+Cluster administrators can also open an embedded command-line terminal instance with the web terminal Operator.
+endif::openshift-rosa-hcp[]
 
 The *Administrator* perspective provides workflows specific to administrator use cases, such as the ability to:
 

modules/about-developer_web-console.adoc

@@ -13,15 +13,30 @@ The developer role in the web console offers several built-in ways to deploy app
 * Share your project with others.
 * Troubleshoot problems with your applications by running Prometheus Query Language (PromQL) queries on your project and examining the metrics visualized on a plot. The metrics provide information about the state of a cluster and any user-defined workloads that you are monitoring.
 
+ifndef::openshift-rosa-hcp[]
 Cluster administrators can also open an embedded command-line terminal instance in the web console in {product-title} 4.7 and later.
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa-hcp[]
+Cluster developers can also open an embedded command-line terminal instance in the web console.
+endif::openshift-rosa-hcp[]
 
 Developers have access to workflows specific to their use cases, such as the ability to:
 
-* Create and deploy applications on {product-title} by importing existing codebases, images, and container files.
+* Create and deploy applications on 
+ifndef::openshift-rosa-hcp,openshift-rosa[]
+{product-title} 
+endif::openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-rosa-hcp[]
+{rosa-short} 
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa[]
+{rosa-classic-short} 
+endif::openshift-rosa[]
+by importing existing codebases, images, and container files.
 * Visually interact with applications, components, and services associated with them within a project and monitor their deployment and build status.
 * Group components within an application and connect the components within and across applications.
 * Integrate serverless capabilities (Technology Preview).
-* Create workspaces to edit your application code using Eclipse Che.
+* Create workspaces to edit their application code using Eclipse Che.
 
 You can use the *Topology* view to display applications, components, and workloads of your project. If you have no workloads in the project, the *Topology* view will show some links to create or import them. You can also use the *Quick Search* to import components directly.
 

modules/adding-tab-pods-page.adoc

@@ -10,7 +10,17 @@ There are different customizations you can make to the {product-title} web conso
 
 [NOTE]
 ====
-The {product-title} web console runs in a container connected to the cluster you have logged into. See "Dynamic plugin development" for information to test the plugin before creating your own.
+The 
+ifndef::openshift-rosa-hcp,openshift-rosa[]
+{product-title} 
+endif::openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-rosa-hcp[]
+{rosa-short} 
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa[]
+{rosa-classic-short} 
+endif::openshift-rosa[] 
+web console runs in a container connected to the cluster you have logged into. See "Dynamic plugin development" for information to test the plugin before creating your own.
 ====
 
 .Procedure

modules/deployment-plug-in-cluster.adoc

@@ -34,10 +34,18 @@ Where:
 `--set plugin.image=my-plugin-image-location`:: Specifies the location of the image within the `plugin.image` parameter.
 --
 +
+ifndef::openshift-rosa-hcp[]
 [NOTE]
 ====
 If you are deploying on {product-title} 4.10 and later, it is recommended to exclude configurations related to pod security by adding the parameter `--set plugin.securityContext.enabled=false`.
 ====
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa-hcp[]
+[NOTE]
+====
+If you are deploying on {product-title}, it is recommended to exclude configurations related to pod security by adding the parameter `--set plugin.securityContext.enabled=false`.
+====
+endif::openshift-rosa-hcp[]
 
 . Optional: You can specify any additional parameters by using the set of supported parameters in the `charts/openshift-console-plugin/values.yaml` file.
 +

modules/dynamic-plug-in-development.adoc

@@ -15,7 +15,17 @@ You can run the plugin using a local development environment. The {product-title
 ====
 Red{nbsp}Hat does not support custom plugin code. Only link:https://access.redhat.com/solutions/5893251[Cooperative community support] is available for your plugin.
 ====
-* You must have an {product-title} cluster running.
+* You must have 
+ifndef::openshift-rosa-hcp,openshift-rosa[]
+an {product-title} 
+endif::openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-rosa-hcp[]
+a {rosa-short} 
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa[]
+a {rosa-classic-short} 
+endif::openshift-rosa[]
+cluster running.
 * You must have the {oc-first} installed.
 * You must have link:https://yarnpkg.com/[`yarn`] installed.
 * You must have link:https://www.docker.com/[Docker] v3.2.0 or later or link:https://podman.io/[Podman] v3.2.0 or later installed and running.
@@ -40,14 +50,34 @@ $ yarn install
 $ yarn run start
 ----
 
-. In another terminal window, login to the {product-title} through the CLI.
+. In another terminal window, login to the 
+ifndef::openshift-rosa-hcp,openshift-rosa[]
+{product-title} 
+endif::openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-rosa-hcp[]
+{rosa-short} 
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa[]
+{rosa-classic-short} 
+endif::openshift-rosa[]
+through the CLI.
 +
 [source,terminal]
 ----
 $ oc login
 ----
 
-. Run the {product-title} web console in a container connected to the cluster you have logged into by running the following command:
+. Run the
+ifndef::openshift-rosa-hcp,openshift-rosa[]
+{product-title} 
+endif::openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-rosa-hcp[]
+{rosa-short} 
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa[]
+{rosa-classic-short} 
+endif::openshift-rosa[]
+web console in a container connected to the cluster you have logged in to by running the following command:
 +
 [source,terminal]
 ----

modules/dynamic-plugin-localization.adoc

@@ -10,7 +10,8 @@ The link:https://github.com/openshift/console-plugin-template[plugin template] d
 
 .Prerequisites
 * You must have the plugin template cloned locally.
-* Optional: To test your plugin locally, run the {product-title} web console in a container. You can use either Docker or Podman 3.2.0 or later.
+* Optional: To test your plugin locally, run the 
+{product-title} web console in a container. You can use either Docker or Podman 3.2.0 or later.
 
 .Procedure
 

modules/dynamic-plugin-proxy-service.adoc

@@ -39,7 +39,17 @@ spec:
 +
 [NOTE]
 ====
-If the service proxy request does not contain the logged-in user's {product-title} access token, set the authorization field to `None`.
+If the service proxy request does not contain the logged-in user's 
+ifndef::openshift-rosa-hcp,openshift-rosa[]
+{product-title} 
+endif::openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-rosa-hcp[]
+{rosa-short} 
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa[]
+{rosa-classic-short} 
+endif::openshift-rosa[]
+access token, set the authorization field to `None`.
 ====
 <3> If the service uses a custom service CA, the `caCertificate` field must contain the certificate bundle.
 <4> Endpoint of the proxy.

modules/enabling-developer-perspective_web-console.adoc

@@ -6,8 +6,12 @@
 [id="enabling-developer-perspective_web-console_{context}"]
 = Enabling the *Developer* perspective in the web console
 
-
+ifndef::openshift-rosa-hcp[]
 Starting with {product-title} 4.19, the perspectives in the web console have unified. There is no longer a *Developer* perspective by default; however, cluster administrators can enable the *Developer* perspective for developers to use.
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa-hcp[]
+Cluster administrators can enable the *Developer* perspective for developers to use.
+endif::openshift-rosa-hcp[]
 
 You can enable the *Developer* perspective with the following steps:
 

modules/odc-access-web-terminal.adoc

@@ -12,7 +12,14 @@ The web terminal remains open until you close it or until you close the browser
 
 .Prerequisites
 
-* You have access to an {product-title} cluster and are logged into the web console.
+* You have access to 
+ifndef::openshift-rosa-hcp,openshift-rosa[]
+an {product-title} 
+endif::openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-rosa-hcp,openshift-rosa[]
+a {product-title} 
+endif::openshift-rosa-hcp,openshift-rosa[]
+cluster and are logged into the web console.
 * The {web-terminal-op} is installed on your cluster.
 
 .Procedure