Various changes based on testing procedures in Nodes bucket

Author: mburke5678

_topic_map.yml

@@ -416,6 +416,8 @@ Topics:
 - Name: Working with nodes
   Dir: nodes
   Topics:
+  - Name: Viewing and listing the nodes in your cluster
+    File: nodes-nodes-viewing
   - Name: Working with nodes
     File: nodes-nodes-working
   - Name: Managing Nodes
@@ -424,10 +426,6 @@ Topics:
     File: nodes-nodes-managing-max-pods
   - Name: Using the Node Tuning Operator
     File: nodes-node-tuning-operator
-  - Name: Modifying existing nodes
-    File: nodes-nodes-modifying
-  - Name: Viewing and listing the nodes in your cluster
-    File: nodes-nodes-viewing
   - Name: Understanding node rebooting
     File: nodes-nodes-rebooting
   - Name: Freeing node resources using garbage collection

admission-config.yaml

@@ -0,0 +1,5 @@
+kind: AdmissionConfiguration
+apiVersion: apiserver.k8s.io/v1alpha1
+plugins:
+- name: RunOnceDurationConfig
+  activeDeadlineSecondsOverride: 3600 

modules/nodes-cluster-overcommit-configure-nodes.adoc

@@ -4,7 +4,7 @@
 
 [id="nodes-cluster-overcommit-configure-nodes-{context}"]
 
-= Configuring nodes for overcommitment
+= Understanding nodes overcommitment
 
 In an overcommitted environment, it is important to properly configure your node to provide best system behavior.
 

modules/nodes-cluster-resource-configure-oom.adoc

@@ -14,11 +14,16 @@ exiting immediately. If the container PID 1 process receives the *SIGKILL*, the
 container will exit immediately. Otherwise, the container behavior is
 dependent on the behavior of the other processes.
 
+For example, a container process exited with code 137, indicating it received a SIGKILL signal.
+
 If the container does not exit immediately, an OOM kill is detectable as
 follows:
 
-. A container process exited with code 137, indicating it received a SIGKILL
-   signal
+. Access the pod using a remote shell:
++
+----
+# oc rsh test
+----
 
 . The oom_kill counter in `/sys/fs/cgroup/memory/memory.oom_control` is
    incremented

modules/nodes-containers-copying-files-procedure.adoc

@@ -33,13 +33,26 @@ use with the `oc rsync` command.
 .Procedure
 
 * To copy a local directory to a pod directory:
-
++
+----
+oc rsync <local-dir> <pod-name>:/<remote-dir>
+----
++
+For example:
++
 ----
 $ oc rsync /home/user/source devpod1234:/src
+
+WARNING: cannot use rsync: rsync not available in container
+status.txt
 ----
 
 * To copy a pod directory to a local directory:
 
 ----
 $ oc rsync devpod1234:/src /home/user/source
+
+oc rsync devpod1234:/src/status.txt /home/user/
+WARNING: cannot use rsync: rsync not available in container
+status.txt
 ----

modules/nodes-containers-events-viewing.adoc

@@ -15,12 +15,29 @@ You can get a list of events in a given project using the CLI.
 $ oc get events [-n <project>] <1>
 ----
 <1> The name of the project.
++
+For example:
++
+----
+$ oc get events -n openshift-config
+
+LAST SEEN   TYPE      REASON                   OBJECT                      MESSAGE
+97m         Normal    Scheduled                pod/dapi-env-test-pod       Successfully assigned openshift-config/dapi-env-test-pod to ip-10-0-171-202.ec2.internal
+97m         Normal    Pulling                  pod/dapi-env-test-pod       pulling image "gcr.io/google_containers/busybox"
+97m         Normal    Pulled                   pod/dapi-env-test-pod       Successfully pulled image "gcr.io/google_containers/busybox"
+97m         Normal    Created                  pod/dapi-env-test-pod       Created container
+9m5s        Warning   FailedCreatePodSandBox   pod/dapi-volume-test-pod    Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_dapi-volume-test-pod_openshift-config_6bc60c1f-452e-11e9-9140-0eec59c23068_0(748c7a40db3d08c07fb4f9eba774bd5effe5f0d5090a242432a73eee66ba9e22): Multus: Err adding pod to network "openshift-sdn": cannot set "openshift-sdn" ifname to "eth0": no netns: failed to Statfs "/proc/33366/ns/net": no such file or directory
+8m31s       Normal    Scheduled                pod/dapi-volume-test-pod    Successfully assigned openshift-config/dapi-volume-test-pod to ip-10-0-171-202.ec2.internal
+----
+
 
 * To view events in your project from the {product-title} console.
 +
 . Launch the {product-title} console.
 +
 . Click *Home* -> *Events* and select your project.
+
+. Move to resource that you want to see events. For example: *Home* -> *Projects* -> <project-name> -> <resource-name>.
 +
-Many other objects, such as pods and deployments, have their own
+Many objects, such as pods and deployments, have their own
 *Events* tab as well, which shows events related to that object.

modules/nodes-containers-init-creating.adoc

@@ -11,6 +11,7 @@ The following example outlines a simple Pod which has two Init Containers. The f
 
 . Create a YAML file for the Init Container:
 +
+[source-yaml]
 ----
 apiVersion: v1
 kind: Pod
@@ -34,6 +35,7 @@ spec:
 
 . Create a YAML file for the `myservice` service.
 +
+[source-yaml]
 ----
 kind: Service
 apiVersion: v1

modules/nodes-containers-port-forwarding-using.adoc

@@ -21,18 +21,29 @@ For example:
 +
 ----
 $ oc port-forward <pod> 5000 6000
+
+Forwarding from 127.0.0.1:5000 -> 5000
+Forwarding from [::1]:5000 -> 5000
+Forwarding from 127.0.0.1:6000 -> 6000
+Forwarding from [::1]:6000 -> 6000
 ----
 
 * Use the following command to listen on port `8888` locally and forward to `5000` in the pod:
 +
 ----
 $ oc port-forward <pod> 8888:5000
+
+Forwarding from 127.0.0.1:8888 -> 5000
+Forwarding from [::1]:8888 -> 5000
 ----
 
 * Use the following command to listen on a free port locally and forward to `5000` in the pod:
 +
 ----
 $ oc port-forward <pod> :5000
+
+Forwarding from 127.0.0.1:42390 -> 5000
+Forwarding from [::1]:42390 -> 5000
 ----
 +
 Or:

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

@@ -13,15 +13,7 @@ The following example shows how to use a projected volume to mount an existing S
 
 To use a projected volume to mount an existing Secret volume source.
 
-. Create files containing the secrets:
-+
-For example:
-+
-----
-$ nano secret.yaml
-----
-+
-Enter the following, replacing the password and user information as appropriate:
+. Create files containing the secrets, entering the following, replacing the password and user information as appropriate:
 +
 [source,yaml]
 ----
@@ -117,11 +109,12 @@ spec:
   - name: all-in-one
     projected:
       sources:
-      - secret:
+      - secret:      <1>
           name: user
-      - secret:
+      - secret:      <1>
           name: pass
 ----
+<1> The name of the secret you created.
 
 . Create the pod from the configuration file:
 +

modules/nodes-nodes-garbage-collection-configuring.adoc

@@ -1,3 +1,4 @@
+
 // Module included in the following assemblies:
 //
 // * nodes/nodes-nodes-garbage-collection.adoc
@@ -34,7 +35,7 @@ metadata:
 ----
 <1> If a label has been added it appears under `labels`.
 
-.. If the label is not present, add a key/value pair:
+.. If a label is not present, add a key/value pair:
 +
 ----
 $ oc label machineconfigpool worker custom-kubelet=small-pods
@@ -65,3 +66,10 @@ spec:
 <3> Specify the minimum age for an unused image before it is garbage collected. A value of `0` means no limit.
 <4> Specify the percent of disk usage after which image garbage collection is always run.
 <5> Specify the percent of disk usage before which image garbage collection is never run.
+
+. Create the garbage collection object:
++
+----
+oc create -f <file-name>.yaml
+----
+