diff --git a/modules/dr-recover-lost-control-plane-hosts.adoc b/modules/dr-recover-lost-control-plane-hosts.adoc index 3fc23f6844..b4fe03ee34 100644 --- a/modules/dr-recover-lost-control-plane-hosts.adoc +++ b/modules/dr-recover-lost-control-plane-hosts.adoc @@ -74,8 +74,11 @@ In a terminal that has access to the cluster, run the following command to verif + ---- $ oc get nodes -l node-role.kubernetes.io/master -NAME STATUS ROLES AGE VERSION -ip-10-0-143-125.us-east-2.compute.internal Ready master 46m v1.14.6+c4799753c + +NAME STATUS ROLES AGE VERSION +ip-10-0-141-129.ec2.internal Ready master 72m v1.16.2 +ip-10-0-141-69.ec2.internal Ready master 72m v1.16.2 +ip-10-0-148-252.ec2.internal Ready master 72m v1.16.2 ---- + [NOTE] @@ -122,10 +125,11 @@ Be sure to approve both the pending client and server CSR for each master that w + ---- $ oc get nodes -l node-role.kubernetes.io/master -NAME STATUS ROLES AGE VERSION -ip-10-0-143-125.us-east-2.compute.internal Ready master 50m v1.14.6+c4799753c -ip-10-0-156-255.us-east-2.compute.internal Ready master 92s v1.14.6+c4799753c -ip-10-0-162-178.us-east-2.compute.internal Ready master 70s v1.14.6+c4799753c + +NAME STATUS ROLES AGE VERSION +ip-10-0-141-129.ec2.internal Ready master 72m v1.16.2 +ip-10-0-141-69.ec2.internal Ready master 72m v1.16.2 +ip-10-0-148-252.ec2.internal Ready master 72m v1.16.2 ---- . Correct the DNS entries. diff --git a/modules/images-configuration-registry-mirror.adoc b/modules/images-configuration-registry-mirror.adoc index 4784e1356e..1adcc587b6 100644 --- a/modules/images-configuration-registry-mirror.adoc +++ b/modules/images-configuration-registry-mirror.adoc @@ -123,13 +123,13 @@ go to one of your nodes. For example: + ---- $ oc get node -NAME STATUS ROLES AGE VERSION -ip-10-0-137-44.ec2.internal Ready worker 7m v1.14.6+90fadebfa -ip-10-0-138-148.ec2.internal Ready master 11m v1.14.6+90fadebfa -ip-10-0-139-122.ec2.internal Ready master 11m v1.14.6+90fadebfa -ip-10-0-147-35.ec2.internal Ready,SchedulingDisabled worker 7m v1.14.6+90fadebfa -ip-10-0-153-12.ec2.internal Ready worker 7m v1.14.6+90fadebfa -ip-10-0-154-10.ec2.internal Ready master 11m v1.14.6+90fadebfa +NAME STATUS ROLES AGE VERSION +ip-10-0-128-213.ec2.internal Ready worker 59m v1.16.2 +ip-10-0-130-162.ec2.internal Ready worker 60m v1.16.2 +ip-10-0-136-29.ec2.internal Ready master 66m v1.16.2 +ip-10-0-142-198.ec2.internal Ready master 66m v1.16.2 +ip-10-0-149-229.ec2.internal Ready master 66m v1.16.2 +ip-10-0-149-52.ec2.internal Ready worker 60m v1.16.2 ---- + You can see that scheduling on each worker node is disabled as the change is being applied. diff --git a/modules/infrastructure-moving-router.adoc b/modules/infrastructure-moving-router.adoc index ecb65f4cbb..5588d1b9bc 100644 --- a/modules/infrastructure-moving-router.adoc +++ b/modules/infrastructure-moving-router.adoc @@ -86,8 +86,8 @@ In this example, the running pod is on the `ip-10-0-217-226.ec2.internal` node. ---- $ oc get node <1> -NAME STATUS ROLES AGE VERSION -ip-10-0-217-226.ec2.internal Ready infra,worker 17h v1.14.6+c4799753c +NAME STATUS ROLES AGE VERSION +ip-10-0-129-189.ec2.internal Ready worker 70m v1.16.2 ---- <1> Specify the `` that you obtained from the pod list. + diff --git a/modules/installation-approve-csrs.adoc b/modules/installation-approve-csrs.adoc index c6d397f7dd..d5c80390d0 100644 --- a/modules/installation-approve-csrs.adoc +++ b/modules/installation-approve-csrs.adoc @@ -29,12 +29,13 @@ these CSRs are approved or, if necessary, approve them yourself. ---- $ oc get nodes -NAME STATUS ROLES AGE VERSION -master-0 Ready master 63m v1.14.6+c4799753c -master-1 Ready master 63m v1.14.6+c4799753c -master-2 Ready master 64m v1.14.6+c4799753c -worker-0 NotReady worker 76s v1.14.6+c4799753c -worker-1 NotReady worker 70s v1.14.6+c4799753c +NAME STATUS ROLES AGE VERSION +ip-10-0-129-189.ec2.internal Ready worker 65m v1.16.2 +ip-10-0-133-88.ec2.internal Ready worker 65m v1.16.2 +ip-10-0-141-129.ec2.internal Ready master 72m v1.16.2 +ip-10-0-141-69.ec2.internal Ready master 72m v1.16.2 +ip-10-0-146-242.ec2.internal Ready worker 65m v1.16.2 +ip-10-0-148-252.ec2.internal Ready master 72m v1.16.2 ---- + The output lists all of the machines that you created. diff --git a/modules/looking-inside-nodes.adoc b/modules/looking-inside-nodes.adoc index 21c8ec5beb..27d7f0c90f 100644 --- a/modules/looking-inside-nodes.adoc +++ b/modules/looking-inside-nodes.adoc @@ -9,27 +9,26 @@ Directly accessing a node is strongly discouraged. Nodes are meant to be managed For debugging purposes, the oc debug command lets you go inside any pod and look around. For nodes, in particular, you open a tools pod on the node, then chroot to the node’s host filesystem. At that point, you are effectively working on the node. Here’s how to do that: +---- $ oc get nodes -NAME                                     STATUS  ROLES  AGE    VERSION - -ip-10-0-0-1.us-east-2.compute.internal   Ready   worker 3h19m  v1.14.6+c4799753c - -ip-10-0-0-39.us-east-2.compute.internal  Ready   master 3h37m  v1.14.6+c4799753c - -…   - -$ oc debug nodes/ip-10-0-138-39.us-east-2.compute.internal - -Starting pod/ip-10-0-138-39us-east-2computeinternal-debug …​ +NAME STATUS ROLES AGE VERSION +ip-10-0-129-189.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-133-88.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-141-129.ec2.internal Ready master 76m v1.16.2 +ip-10-0-141-69.ec2.internal Ready master 76m v1.16.2 +ip-10-0-146-242.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-148-252.ec2.internal Ready master 76m v1.16.2 +---- +---- +$ oc debug nodes/ip-10-0-129-189.ec2.internal +Starting pod/ip-10-0-129-189ec2internal-debug ... To use host binaries, run `chroot /host` - -If you don’t see a command prompt, try pressing enter. - -sh-4.2# - -  +Pod IP: 10.0.129.189 +If you don't see a command prompt, try pressing enter. +sh-4.2# +---- As noted, you can change to the root of the node’s filesystem by typing chroot /host and running commands from the host on that filesystem as though you were logged in directly from the host. Here are some examples of commands you can run to see what is happening on the node: diff --git a/modules/nodes-nodes-kernel-arguments.adoc b/modules/nodes-nodes-kernel-arguments.adoc index 4e95b7db93..7ab0fdd1d7 100644 --- a/modules/nodes-nodes-kernel-arguments.adoc +++ b/modules/nodes-nodes-kernel-arguments.adoc @@ -115,14 +115,14 @@ rendered-worker-18ff9506c718be1e8bd0a066850065b7 577c2d527b09cd7a481a . Check the nodes: + ---- -$ oc get node -NAME STATUS ROLES AGE VERSION -ip-10-0-136-161.ec2.internal Ready worker 28m v1.14.6+90fadebfa -ip-10-0-136-243.ec2.internal Ready master 34m v1.14.6+90fadebfa -ip-10-0-141-105.ec2.internal Ready,SchedulingDisabled worker 28m v1.14.6+90fadebfa -ip-10-0-142-249.ec2.internal Ready master 34m v1.14.6+90fadebfa -ip-10-0-153-11.ec2.internal Ready worker 28m v1.14.6+90fadebfa -ip-10-0-153-150.ec2.internal Ready master 34m v1.14.6+90fadebfa +$ oc get nodes +NAME STATUS ROLES AGE VERSION +ip-10-0-129-189.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-133-88.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-141-129.ec2.internal Ready master 76m v1.16.2 +ip-10-0-141-69.ec2.internal Ready master 76m v1.16.2 +ip-10-0-146-242.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-148-252.ec2.internal Ready master 76m v1.16.2 ---- + You can see that scheduling on each worker node is disabled as the change is being applied. diff --git a/modules/nodes-nodes-viewing-listing.adoc b/modules/nodes-nodes-viewing-listing.adoc index 0ae599971f..66682e46f9 100644 --- a/modules/nodes-nodes-viewing-listing.adoc +++ b/modules/nodes-nodes-viewing-listing.adoc @@ -12,10 +12,13 @@ You can get detailed information on the nodes in the cluster. ---- $ oc get nodes -NAME STATUS ROLES AGE VERSION -master.example.com Ready master 7h v1.14.6+c4799753c -node1.example.com Ready worker 7h v1.14.6+c4799753c -node2.example.com Ready worker 7h v1.14.6+c4799753c +NAME STATUS ROLES AGE VERSION +ip-10-0-129-189.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-133-88.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-141-129.ec2.internal Ready master 76m v1.16.2 +ip-10-0-141-69.ec2.internal Ready master 76m v1.16.2 +ip-10-0-146-242.ec2.internal Ready worker 69m v1.16.2 +ip-10-0-148-252.ec2.internal Ready master 76m v1.16.2 ---- * The `-wide` option provides additional information on all nodes. @@ -114,9 +117,9 @@ System Info: <9> OS Image: Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) Operating System: linux Architecture: amd64 - Container Runtime Version: cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8 - Kubelet Version: v1.14.6+c4799753c - Kube-Proxy Version: v1.14.6+c4799753c + Container Runtime Version: cri-o://1.16.0-0.6.dev.rhaos4.3.git9ad059b.el8-rc2 + Kubelet Version: v1.16.2 + Kube-Proxy Version: v1.16.2 PodCIDR: 10.128.4.0/24 ProviderID: aws:///us-east-2a/i-04e87b31dc6b3e171 Non-terminated Pods: (13 in total) <10> diff --git a/modules/nodes-nodes-working-evacuating.adoc b/modules/nodes-nodes-working-evacuating.adoc index ace2d7b15d..8069a82957 100644 --- a/modules/nodes-nodes-working-evacuating.adoc +++ b/modules/nodes-nodes-working-evacuating.adoc @@ -21,8 +21,11 @@ Nodes must first be marked unschedulable to perform pod evacuation. ---- $ oc adm cordon +node/ cordoned + +$ oc get node NAME STATUS ROLES AGE VERSION - NotReady,SchedulingDisabled worker 1d v1.14.6+c4799753c + NotReady,SchedulingDisabled worker 1d v1.16.2 ---- Use `oc adm uncordon` to mark the node as schedulable when done. diff --git a/modules/understanding-workers-masters.adoc b/modules/understanding-workers-masters.adoc index 1c19d08822..4382aff857 100644 --- a/modules/understanding-workers-masters.adoc +++ b/modules/understanding-workers-masters.adoc @@ -12,13 +12,13 @@ To see which workers and masters are running on your cluster, type: ---- $ oc get nodes -NAME                                   STATUS ROLES  AGE    VERSION -ip-10-0-0-1.us-east-2.compute.internal Ready  worker 4h20m  v1.14.6+c4799753c -ip-10-0-0-2.us-east-2.compute.internal Ready  master 4h39m  v1.14.6+c4799753c -ip-10-0-0.3.us-east-2.compute.internal Ready  worker 4h20m  v1.14.6+c4799753c -ip-10-0-0-4.us-east-2.compute.internal Ready  master 4h39m  v1.14.6+c4799753c -ip-10-0-0-5.us-east-2.compute.internal Ready  master 4h39m  v1.14.6+c4799753c -ip-10-0-0-6.us-east-2.compute.internal Ready  worker 4h20m  v1.14.6+c4799753c +NAME STATUS ROLES AGE VERSION +ip-10-0-129-189.ec2.internal Ready,SchedulingDisabled worker 81m v1.16.2 +ip-10-0-133-88.ec2.internal Ready worker 81m v1.16.2 +ip-10-0-141-129.ec2.internal Ready master 88m v1.16.2 +ip-10-0-141-69.ec2.internal Ready master 88m v1.16.2 +ip-10-0-146-242.ec2.internal Ready worker 80m v1.16.2 +ip-10-0-148-252.ec2.internal Ready master 88m v1.16.2 ---- To see more information about internal and external IP addresses, the type of operating system ({op-system}), kernel version, and container runtime (CRI-O), add the `-o wide` option. @@ -31,7 +31,8 @@ NAME                                       STATUS ROLES  AGE       OS-IMAGE             KERNEL-VERSION            CONTAINER-RUNTIME -ip-10-0-134-252.us-east-2.compute.internal Ready  worker 17h  v1.14.6+c4799753c   + - 10.0.134.252   + -     Red Hat CoreOS 4.0   3.10.0-957.5.1.el7.x86_64 cri-o://1.13.6-1.rhaos4.0.git2f0cb0d.el7 +NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME +ip-10-0-129-189.ec2.internal Ready,SchedulingDisabled worker 81m v1.16.2 10.0.129.189 Red Hat Enterprise Linux CoreOS 43.81.201911071053.0 (Ootpa) 4.18.0-147.el8.x86_64 cri-o://1.16.0-0.6.dev.rhaos4.3.git9ad059b.el8-rc2 + +.... ----