mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Update Kubernetes to 1.17 version in outputs
This commit is contained in:
Michael Burke
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
b1936c58d7
commit
3dc3442158
@@ -77,7 +77,7 @@ 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.16.2
|
||||
ip-10-0-143-125.us-east-2.compute.internal Ready master 46m v1.17.1
|
||||
----
|
||||
+
|
||||
[NOTE]
|
||||
@@ -125,9 +125,9 @@ 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.16.2
|
||||
ip-10-0-156-255.us-east-2.compute.internal Ready master 92s v1.16.2
|
||||
ip-10-0-162-178.us-east-2.compute.internal Ready master 70s v1.16.2
|
||||
ip-10-0-143-125.us-east-2.compute.internal Ready master 50m v1.17.1
|
||||
ip-10-0-156-255.us-east-2.compute.internal Ready master 92s v1.17.1
|
||||
ip-10-0-162-178.us-east-2.compute.internal Ready master 70s v1.17.1
|
||||
----
|
||||
|
||||
. Correct the DNS entries.
|
||||
|
||||
@@ -124,12 +124,12 @@ 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.16.2
|
||||
ip-10-0-138-148.ec2.internal Ready master 11m v1.16.2
|
||||
ip-10-0-139-122.ec2.internal Ready master 11m v1.16.2
|
||||
ip-10-0-147-35.ec2.internal Ready,SchedulingDisabled worker 7m v1.16.2
|
||||
ip-10-0-153-12.ec2.internal Ready worker 7m v1.16.2
|
||||
ip-10-0-154-10.ec2.internal Ready master 11m v1.16.2
|
||||
ip-10-0-137-44.ec2.internal Ready worker 7m v1.17.1
|
||||
ip-10-0-138-148.ec2.internal Ready master 11m v1.17.1
|
||||
ip-10-0-139-122.ec2.internal Ready master 11m v1.17.1
|
||||
ip-10-0-147-35.ec2.internal Ready,SchedulingDisabled worker 7m v1.17.1
|
||||
ip-10-0-153-12.ec2.internal Ready worker 7m v1.17.1
|
||||
ip-10-0-154-10.ec2.internal Ready master 11m v1.17.1
|
||||
----
|
||||
+
|
||||
You can see that scheduling on each worker node is disabled as the change is being applied.
|
||||
|
||||
@@ -87,7 +87,7 @@ In this example, the running pod is on the `ip-10-0-217-226.ec2.internal` node.
|
||||
$ oc get node <node_name> <1>
|
||||
|
||||
NAME STATUS ROLES AGE VERSION
|
||||
ip-10-0-217-226.ec2.internal Ready infra,worker 17h v1.16.2
|
||||
ip-10-0-217-226.ec2.internal Ready infra,worker 17h v1.17.1
|
||||
----
|
||||
<1> Specify the `<node_name>` that you obtained from the pod list.
|
||||
+
|
||||
|
||||
@@ -48,11 +48,11 @@ ifndef::ibm-z[]
|
||||
$ oc get nodes
|
||||
|
||||
NAME STATUS ROLES AGE VERSION
|
||||
master-0 Ready master 63m v1.16.2
|
||||
master-1 Ready master 63m v1.16.2
|
||||
master-2 Ready master 64m v1.16.2
|
||||
worker-0 NotReady worker 76s v1.16.2
|
||||
worker-1 NotReady worker 70s v1.16.2
|
||||
master-0 Ready master 63m v1.17.1
|
||||
master-1 Ready master 63m v1.17.1
|
||||
master-2 Ready master 64m v1.17.1
|
||||
worker-0 NotReady worker 76s v1.17.1
|
||||
worker-1 NotReady worker 70s v1.17.1
|
||||
----
|
||||
endif::ibm-z[]
|
||||
+
|
||||
|
||||
@@ -14,9 +14,9 @@ $ oc get nodes
|
||||
|
||||
NAME STATUS ROLES AGE VERSION
|
||||
|
||||
ip-10-0-0-1.us-east-2.compute.internal Ready worker 3h19m v1.16.2
|
||||
ip-10-0-0-1.us-east-2.compute.internal Ready worker 3h19m v1.17.1
|
||||
|
||||
ip-10-0-0-39.us-east-2.compute.internal Ready master 3h37m v1.16.2
|
||||
ip-10-0-0-39.us-east-2.compute.internal Ready master 3h37m v1.17.1
|
||||
|
||||
…
|
||||
|
||||
|
||||
@@ -117,12 +117,12 @@ rendered-worker-18ff9506c718be1e8bd0a066850065b7 577c2d527b09cd7a481a
|
||||
----
|
||||
$ oc get nodes
|
||||
NAME STATUS ROLES AGE VERSION
|
||||
ip-10-0-136-161.ec2.internal Ready worker 28m v1.16.2
|
||||
ip-10-0-136-243.ec2.internal Ready master 34m v1.16.2
|
||||
ip-10-0-141-105.ec2.internal Ready,SchedulingDisabled worker 28m v1.16.2
|
||||
ip-10-0-142-249.ec2.internal Ready master 34m v1.16.2
|
||||
ip-10-0-153-11.ec2.internal Ready worker 28m v1.16.2
|
||||
ip-10-0-153-150.ec2.internal Ready master 34m v1.16.2
|
||||
ip-10-0-136-161.ec2.internal Ready worker 28m v1.17.1
|
||||
ip-10-0-136-243.ec2.internal Ready master 34m v1.17.1
|
||||
ip-10-0-141-105.ec2.internal Ready,SchedulingDisabled worker 28m v1.17.1
|
||||
ip-10-0-142-249.ec2.internal Ready master 34m v1.17.1
|
||||
ip-10-0-153-11.ec2.internal Ready worker 28m v1.17.1
|
||||
ip-10-0-153-150.ec2.internal Ready master 34m v1.17.1
|
||||
----
|
||||
+
|
||||
You can see that scheduling on each worker node is disabled as the change is being applied.
|
||||
|
||||
@@ -13,9 +13,9 @@ 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.16.2
|
||||
node1.example.com Ready worker 7h v1.16.2
|
||||
node2.example.com Ready worker 7h v1.16.2
|
||||
master.example.com Ready master 7h v1.17.1
|
||||
node1.example.com Ready worker 7h v1.17.1
|
||||
node2.example.com Ready worker 7h v1.17.1
|
||||
----
|
||||
|
||||
* The `-wide` option provides additional information on all nodes.
|
||||
@@ -115,8 +115,8 @@ System Info: <9>
|
||||
Operating System: linux
|
||||
Architecture: amd64
|
||||
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
|
||||
Kubelet Version: v1.17.1
|
||||
Kube-Proxy Version: v1.17.1
|
||||
PodCIDR: 10.128.4.0/24
|
||||
ProviderID: aws:///us-east-2a/i-04e87b31dc6b3e171
|
||||
Non-terminated Pods: (13 in total) <10>
|
||||
|
||||
@@ -25,7 +25,7 @@ node/<node1> cordoned
|
||||
|
||||
$ oc get node <node1>
|
||||
NAME STATUS ROLES AGE VERSION
|
||||
<node1> NotReady,SchedulingDisabled worker 1d v1.16.2
|
||||
<node1> NotReady,SchedulingDisabled worker 1d v1.17.1
|
||||
----
|
||||
|
||||
Use `oc adm uncordon` to mark the node as schedulable when done.
|
||||
|
||||
@@ -65,9 +65,9 @@ You must not enable firewalld later. If you do, you cannot access {product-title
|
||||
----
|
||||
# oc get node
|
||||
NAME STATUS ROLES AGE VERSION
|
||||
mycluster-control-plane-0 Ready master 145m v1.16.2
|
||||
mycluster-control-plane-1 Ready master 145m v1.16.2
|
||||
mycluster-control-plane-2 Ready master 145m v1.16.2
|
||||
mycluster-control-plane-0 Ready master 145m v1.17.1
|
||||
mycluster-control-plane-1 Ready master 145m v1.17.1
|
||||
mycluster-control-plane-2 Ready master 145m v1.17.1
|
||||
mycluster-rhel7-0 NotReady,SchedulingDisabled worker 98m v1.14.6+97c81d00e
|
||||
mycluster-rhel7-1 Ready worker 98m v1.14.6+97c81d00e
|
||||
mycluster-rhel7-2 Ready worker 98m v1.14.6+97c81d00e
|
||||
@@ -106,11 +106,11 @@ that you created.
|
||||
----
|
||||
# oc get node
|
||||
NAME STATUS ROLES AGE VERSION
|
||||
mycluster-control-plane-0 Ready master 145m v1.16.2
|
||||
mycluster-control-plane-1 Ready master 145m v1.16.2
|
||||
mycluster-control-plane-2 Ready master 145m v1.16.2
|
||||
mycluster-rhel7-0 NotReady,SchedulingDisabled worker 98m v1.16.2
|
||||
mycluster-rhel7-1 Ready worker 98m v1.16.2
|
||||
mycluster-rhel7-2 Ready worker 98m v1.16.2
|
||||
mycluster-rhel7-3 Ready worker 98m v1.16.2
|
||||
mycluster-control-plane-0 Ready master 145m v1.17.1
|
||||
mycluster-control-plane-1 Ready master 145m v1.17.1
|
||||
mycluster-control-plane-2 Ready master 145m v1.17.1
|
||||
mycluster-rhel7-0 NotReady,SchedulingDisabled worker 98m v1.17.1
|
||||
mycluster-rhel7-1 Ready worker 98m v1.17.1
|
||||
mycluster-rhel7-2 Ready worker 98m v1.17.1
|
||||
mycluster-rhel7-3 Ready worker 98m v1.17.1
|
||||
----
|
||||
|
||||
@@ -13,12 +13,12 @@ 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.16.2
|
||||
ip-10-0-0-2.us-east-2.compute.internal Ready master 4h39m v1.16.2
|
||||
ip-10-0-0.3.us-east-2.compute.internal Ready worker 4h20m v1.16.2
|
||||
ip-10-0-0-4.us-east-2.compute.internal Ready master 4h39m v1.16.2
|
||||
ip-10-0-0-5.us-east-2.compute.internal Ready master 4h39m v1.16.2
|
||||
ip-10-0-0-6.us-east-2.compute.internal Ready worker 4h20m v1.16.2
|
||||
ip-10-0-0-1.us-east-2.compute.internal Ready worker 4h20m v1.17.1
|
||||
ip-10-0-0-2.us-east-2.compute.internal Ready master 4h39m v1.17.1
|
||||
ip-10-0-0.3.us-east-2.compute.internal Ready worker 4h20m v1.17.1
|
||||
ip-10-0-0-4.us-east-2.compute.internal Ready master 4h39m v1.17.1
|
||||
ip-10-0-0-5.us-east-2.compute.internal Ready master 4h39m v1.17.1
|
||||
ip-10-0-0-6.us-east-2.compute.internal Ready worker 4h20m v1.17.1
|
||||
----
|
||||
|
||||
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.
|
||||
@@ -27,7 +27,7 @@ To see more information about internal and external IP addresses, the type of op
|
||||
$ oc get nodes -o wide
|
||||
|
||||
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
|
||||
ip-10-0-134-252.us-east-2.compute.internal Ready worker 17h v1.16.2 10.0.134.252 <none> Red Hat CoreOS 4.0 3.10.0-957.5.1.el7.x86_64 cri-o://1.13.6-1.rhaos4.0.git2f0cb0d.el7
|
||||
ip-10-0-134-252.us-east-2.compute.internal Ready worker 17h v1.17.1 10.0.134.252 <none> Red Hat CoreOS 4.0 3.10.0-957.5.1.el7.x86_64 cri-o://1.13.6-1.rhaos4.0.git2f0cb0d.el7
|
||||
|
||||
....
|
||||
----
|
||||
|
||||
Reference in New Issue
Block a user