web terminal docs

removed bold from heading

review edits

review edits 2

image tag edit

review edits first part

review edits 2

minor fix

review fix 3

_topic_map.yml

@@ -429,6 +429,8 @@ Topics:
   Distros: openshift-enterprise,openshift-webscale,openshift-origin
 - Name: Developer perspective
   File: odc-about-developer-perspective
+- Name: Web terminal
+  File: odc-about-web-terminal
 - Name: Disabling the web console
   File: disabling-web-console
   Distros: openshift-enterprise,openshift-webscale,openshift-origin

modules/odc-accessing-developer-perspective.adoc

@@ -3,7 +3,7 @@
 // web_console/odc-about-developer-perspective.adoc
 
 [id="accessing-developer-perspective_{context}"]
-= Accessing Developer Perspective
+= Accessing the Developer perspective
 
 The *Developer* perspective in the {product-title} web console provides workflows specific to developer use cases.
 

modules/odc-installing-web-terminal.adoc

@@ -0,0 +1,26 @@
+// Module included in the following assemblies:
+//
+// web_console/odc-about-web-terminal.adoc
+
+[id="odc-installing-web-terminal_{context}"]
+= Installing the web terminal
+
+You can install the web terminal using the Web Terminal Operator listed in the {product-title} OperatorHub. When you install the Web Terminal Operator, the custom resource definitions (CRDs) that are required for the command line configuration, such as the `DevWorkspace` CRD, are automatically installed. The web console creates the required resources when you open the web terminal.
+
+.Prerequisites
+* Access to an {product-title} cluster using an account with `cluster-admin` permissions.
+
+.Procedure
+. In the *Administrator* perspective of the web console, navigate to *Operators -> OperatorHub*.
+. Use the *Filter by keyword* box to search for the `Web Terminal` Operator in the catalog, and then click the *Web Terminal* tile.
+. Read the brief description about the Operator on the *Web Terminal*  page, and then click *Install*.
+. On the *Install Operator* page, retain the default values for all fields.
+
+** The *alpha* option in the *Update Channel* menu enables installation of the latest release of the Web Terminal Operator.
+** The *All namespaces on the cluster* option in the *Installation Mode* menu  enables the Operator to watch and be available to all namespaces in the cluster.
+** The *openshift-operators* option in the *Installed Namespace* menu installs the Operator in the default `openshift-operators` namespace.
+** The *Automatic* option in the *Approval Strategy* menu ensures that the future upgrades to the Operator are handled automatically by the Operator Lifecycle Manager.
+
+. Click *Install*.
+. In the *Installed Operators* page, click the *View operator* to verify that the Operator is listed on the *Installed Operators* page.
+. After the Operator is installed, refresh your page to see the command line terminal icon on the upper right of the console.

modules/odc-uninstalling-web-terminal.adoc

@@ -0,0 +1,120 @@
+// Module included in the following assemblies:
+//
+// web_console/odc-about-web-terminal.adoc
+
+[id="odc-uninstalling-web-terminal_{context}"]
+= Uninstalling the web terminal
+
+Uninstalling the web terminal is a two-step process:
+
+. Delete the components and custom resources (CRs) that were added when you installed the Operator.
+. Uninstall the Web Terminal Operator.
+
+Uninstalling the Web Terminal Operator does not remove any of its custom resource definitions (CRDs) or managed resources that are created when the Operator is installed. These components must be manually uninstalled for security purposes. Removing these components also allows you to save cluster resources by ensuring that terminals do not idle when the Operator is uninstalled.
+
+.Prerequisites
+* Access to an {product-title} cluster using an account with `cluster-admin` permissions.
+
+== Deleting the web terminal components and custom resources
+
+Use the CLI to delete the CRs that are created during installation of the  Web Terminal Operator.
+
+.Procedure
+. Run the following commands to ensure that all `DevWorkspace` CRs are removed along with their related Kubernetes objects, such as deployments.
++
+[source,terminal]
+----
+$ oc delete devworkspaces.workspace.devfile.io --all-namespaces --all --wait
+----
++
+[source,terminal]
+----
+$ oc delete workspaceroutings.controller.devfile.io --all-namespaces --all --wait
+----
++
+[source,terminal]
+----
+$ oc delete components.controller.devfile.io --all-namespaces --all --wait
+----
++
+[WARNING]
+====
+If this step is not complete, finalizers make it difficult to fully uninstall the Operator easily.
+====
++
+. Run the following commands to remove the CRDs:
++
+[source,terminal]
+----
+$ oc delete customresourcedefinitions.apiextensions.k8s.io workspaceroutings.controller.devfile.io
+----
++
+[source,terminal]
+----
+$ oc delete customresourcedefinitions.apiextensions.k8s.io components.controller.devfile.io
+----
++
+[source,terminal]
+----
+$ oc delete customresourcedefinitions.apiextensions.k8s.io devworkspaces.workspace.devfile.io
+----
++
+. Remove the `DevWorkspace-Webhook-Server` deployment:
++
+[source,terminal]
+----
+$ oc delete deployment/devworkspace-webhook-server -n openshift-operators
+----
++
+[NOTE]
+====
+When you run this and the following steps, you cannot use the `oc exec` commands to run commands in a container. After you remove the webhooks you will be able to use the `oc exec` commands again.
+====
++
+. Run the following commands to remove any lingering services, secrets, and config maps:
++
+[source,terminal]
+----
+$ oc delete all --selector app.kubernetes.io/part-of=devworkspace-operator,app.kubernetes.io/name=devworkspace-webhook-server
+----
++
+[source,terminal]
+----
+$ oc delete serviceaccounts devworkspace-webhook-server -n openshift-operators
+----
++
+[source,terminal]
+----
+$ oc delete configmap devworkspace-controller -n openshift-operators
+----
++
+[source,terminal]
+----
+$ oc delete clusterrole devworkspace-webhook-server
+----
++
+[source,terminal]
+----
+$ oc delete clusterrolebinding devworkspace-webhook-server
+----
++
+. Run the following commands to remove mutating or validating webhook configurations:
++
+[source,terminal]
+----
+$ oc delete mutatingwebhookconfigurations controller.devfile.io
+----
++
+[source,terminal]
+----
+$ oc delete validatingwebhookconfigurations controller.devfile.io
+----
+
+== Uninstalling the Operator using the web console
+
+.Procedure
+
+. In the *Administrator* perspective of the web console, navigate to *Operators -> Installed Operators*.
+. Scroll the filter list or type a keyword into the *Filter by name* box to find the *Web Terminal* Operator.
+. Click the Options menu {kebab} for the Web Terminal Operator, and then select *Uninstall Operator*.
+. In the *Uninstall Operator* confirmation dialog box, click *Uninstall* to remove the Operator, Operator deployments, and pods from the cluster. The Operator stops running and no longer receives updates.

modules/odc-using-web-terminal.adoc

@@ -0,0 +1,21 @@
+// Module included in the following assemblies:
+//
+// web_console/odc-about-web-terminal.adoc
+
+[id="odc-using-web-terminal_{context}"]
+= Using the web terminal
+
+After the Web Terminal Operator is installed, you can use the web terminal as follows:
+
+. To launch the web terminal, click the command line terminal icon (image:odc-wto-icon.png[title="wto icon"]) on the upper right of the console. A web terminal instance is displayed in the *Command line terminal* pane. This instance is automatically logged in with your credentials.
+. Select the project where the `DevWorkspace` CR must be created from the *Project* drop-down list. By default, the current project is selected.
++
+[NOTE]
+====
+* The `DevWorkspace` CR is created only if it does not already exist.
+* The `openshift-terminal` project is the default project used for cluster administrators. They do not have the option to choose another project.
+====
++
+. Click *Start* to initialize the web terminal using the selected project.
+
+After the web terminal is initialized, you can use the preinstalled CLI tools like `oc`, `kubectl`, `odo`, `kn`, `tkn`, `helm`, `kubens`, and `kubectx` in the web terminal.

web_console/odc-about-web-terminal.adoc

@@ -0,0 +1,24 @@
+[id="odc-about-web-terminal"]
+= About the web terminal in the web console
+include::modules/common-attributes.adoc[]
+:context: odc-about-web-terminal
+
+toc::[]
+
+You can launch an embedded command line terminal instance in the OpenShift web console. You must first install the Web Terminal Operator to use the web terminal.
+
+[NOTE]
+====
+Cluster administrators can access the web terminal in {product-title} 4.7 and later.
+====
+
+This terminal instance is preinstalled with common CLI tools for interacting with the cluster, such as `oc`, `kubectl`,`odo`, `kn`, `tkn`, `helm`, `kubens`, and `kubectx`. It also has the context of the project you are working on and automatically logs you in using your credentials.
+
+:FeatureName: Web terminal
+include::modules/technology-preview.adoc[leveloffset=+1]
+
+include::modules/odc-installing-web-terminal.adoc[leveloffset=+1]
+
+include::modules/odc-using-web-terminal.adoc[leveloffset=+1]
+
+include::modules/odc-uninstalling-web-terminal.adoc[leveloffset=+1]