Merge pull request #13578 from mburke5678/nodes-remove-ansible

Removing Ansible from Nodes topics

Author: mburke5678

modules/nodes-containers-projected-volumes-about.adoc

@@ -20,7 +20,7 @@ An application using these resources could be deploying OpenStack on Kubernetes.
 
 *ConfigMap + Secrets.*:: 
 Projected volumes allow you to deploy containers involving configuration data and passwords.
-For example, you might execute an Ansible playbook stored as a configmap, with some sensitive encrypted tasks that are decrypted using a vault password file.
+For example, you might execute a configmap with some sensitive encrypted tasks that are decrypted using a vault password file.
 
 *ConfigMap + Downward API.*::
 Projected volumes allow you to generate a config including the pod name (available via the `metadata.name` selector). This application can then pass the pod name along with requests in order to easily determine the source without using IP tracking.

modules/nodes-nodes-problem-detector-about.adoc

@@ -108,7 +108,5 @@ to catch kernel problems and application crashes on the host.
 The Node Problem Detector consumes resources. If you use the Node Problem Detector, make sure you have enough nodes to balance cluster performance.
 ====
 
-If `openshift_node_problem_detector_install` was set to `true` in the *_/etc/ansible/hosts_* inventory file,
-the installation creates a Node Problem Detector daemonset by default and creates a project for the detector, called `openshift-node-problem-detector`.
 
 

modules/nodes-nodes-problem-detector-installing.adoc

@@ -5,36 +5,31 @@
 [id='nodes-nodes-problem-detector-installing_{context}']
 = Installing the {product-title} node problem detector
 
-If the Node Problem Detector is not installed, you can use an Ansible playbook to install the tool.
-
-[NOTE]
-====
-Because the Node Problem Detector is in Technology Preview, the `openshift_node_problem_detector_install` is set to `false` by default.
-You must manually change the parameter to `true` when installing the Node Problem Detector.
-====
+You can use the {product-title} console to subscribe to the Node Problem Detector subscription, 
+which creates the Node Problem Detector Operator.
 
 .Procedure
 
 To install the Node Problem Detector:
 
-. Change to the playbook directory:
-+
-[source,bash]
-----
-$ cd /usr/share/ansible/openshift-ansible
-----
+.Procedure
 
-. Edit the the *_/etc/ansible/hosts_* inventory file:
-+
-[source,bash]
-----
-openshift_node_problem_detector_install=`true`
-----
+To subscribe to the subscription:
+
+. In the {product-title} console, click *Catalog* -> *Operator Hub* -> *node-problem-detector*.
 
-. Use the following command to run the playbook to install Node Problem Detector:
+. In the *node-problem-detector* overview, click *Install*.
+
+. In *Create Operator Subscription*: 
+
+.. Select the operator.
+
+.. Select the update channel.
+
+.. Select the approval strategy.
++
+*Automatic*. 
 +
-[source,bash]
-----
-$ ansible-playbook playbooks/openshift-node-problem-detector/config.yml
-----
+*Manual*. 
 
+. Click *Subscribe*.

modules/nodes-nodes-problem-detector-uninstalling.adoc

@@ -10,20 +10,3 @@ If you need to remove the Node Problem Detector follow the steps below.
 .Procedure
 
 To uninstall the Node Problem Detector:
-
-. Add following options in Ansible inventory file:
-+
-[source,yaml]
-----
-[OSEv3:vars]
-openshift_node_problem_detector_state=absent
-----
-
-. Change to the playbook directory and run the *_config.yml_* Ansible playbook:
-+
-[source,bash]
-----
-$ cd /usr/share/ansible/openshift-ansible
-$ ansible-playbook playbooks/openshift-node-problem-detector/config.yml
-----
-

modules/nodes-nodes-viewing-listing.adoc

@@ -127,7 +127,7 @@ Non-terminated Pods:                 (14 in total)       <10>
   kube-system                        master-api-m01.example.com            0 (0%)        0 (0%)      0 (0%)           0 (0%)
   kube-system                        master-controllers-m01.example.com    0 (0%)        0 (0%)      0 (0%)           0 (0%)
   kube-system                        master-etcd-m01.example.com           0 (0%)        0 (0%)      0 (0%)           0 (0%)
-  openshift-ansible-service-broker   asb-1-hnn5t                           0 (0%)        0 (0%)      0 (0%)           0 (0%)
+  service-broker                     sb-1-hnn5t                            0 (0%)        0 (0%)      0 (0%)           0 (0%)
   openshift-node                     sync-dvhvs                            0 (0%)        0 (0%)      0 (0%)           0 (0%)
   openshift-sdn                      ovs-zjs5k                             100m (5%)     200m (10%)  300Mi (3%)       400Mi (5%)
   openshift-sdn                      sdn-zr4cb                             100m (5%)     0 (0%)      200Mi (2%)       0 (0%)