You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the previous output, there are three master and three worker nodes. All machines are updated and none are currently updating. Because all nodes are `Updated` and `Ready` and none are `Degraded`, you can tell that there are no issues.
19
+
.Example output
20
+
[source,terminal]
21
+
----
22
+
NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE
UPDATED:: The `True` status indicates that the MCO has applied the current machine config to the nodes in that MCP. The current machine config is specified in the `STATUS` field in the `oc get mcp` output. The `False` status indicates a node in the MCP is updating.
31
+
UPDATING:: The `True` status indicates that the MCO is applying the desired machine config, as specified in the `MachineConfigPool` custom resource, to at least one of the nodes in that MCP. The desired machine config is the new, edited machine config. Nodes that are updating might not be available for scheduling. The `False` status indicates that all nodes in the MCP are updated.
32
+
DEGRADED:: A `True` status indicates the MCO is blocked from applying the current or desired machine config to at least one of the nodes in that MCP, or the configuration is failing. Nodes that are degraded might not be available for scheduling. A `False` status indicates that all nodes in the MCP are ready.
33
+
MACHINECOUNT:: Indicates the total number of machines in that MCP.
34
+
READYMACHINECOUNT:: Indicates the total number of machines in that MCP that are ready for scheduling.
35
+
UPDATEDMACHINECOUNT:: Indicates the total number of machines in that MCP that have the current machine config.
36
+
DEGRADEDMACHINECOUNT:: Indicates the total number of machines in that MCP that are marked as degraded or unreconcilable.
37
+
--
25
38
+
39
+
In the previous output, there are three control plane (master) nodes and three worker nodes. The control plane MCP and the associated nodes are updated to the current machine config. The nodes in the worker MCP are being updated to the desired machine config. Two of the nodes in the worker MCP are updated and one is still updating, as indicated by the `UPDATEDMACHINECOUNT` being `2`. There are no issues, as indicated by the `DEGRADEDMACHINECOUNT` being `0` and `DEGRADED` being `False`.
40
+
+
41
+
While the nodes in the MCP are updating, the machine config listed under `CONFIG` is the current machine config, which the MCP is being updated from. When the update is complete, the listed machine config is the desired machine config, which the MCP was updated to.
42
+
+
43
+
[NOTE]
44
+
====
45
+
If a node is being cordoned, that node is not included in the `READYMACHINECOUNT`, but is included in the `MACHINECOUNT`. Also, the MCP status is set to `UPDATING`. Because the node has the current machine config, it is counted in the `UPDATEDMACHINECOUNT` total:
Note that the `machineconfigs` listed as `rendered` are not meant to be changed or deleted. Expect them to be hidden at some point in the future.
54
+
====
40
55
41
-
. Check the status of worker (or change to master) to see the status of that pool of nodes:
56
+
. To check the status of the nodes in an MCP by examining the `MachineConfigPool` custom resource, run the following command:
57
+
:
42
58
+
43
59
[source,terminal]
44
60
----
45
61
$ oc describe mcp worker
62
+
----
63
+
+
64
+
.Example output
65
+
[source,terminal]
66
+
----
46
67
...
47
68
Degraded Machine Count: 0
48
69
Machine Count: 3
@@ -52,13 +73,58 @@ $ oc describe mcp worker
52
73
Updated Machine Count: 3
53
74
Events: <none>
54
75
----
76
+
+
77
+
[NOTE]
78
+
====
79
+
If a node is being cordoned, the node is not included in the `Ready Machine Count`. It is included in the `Unavailable Machine Count`:
55
80
56
-
. You can view the contents of a particular machine config (in this case, `01-master-kubelet`). The trimmed output from the following `oc describe` command shows that this `machineconfig` contains both configuration files (`cloud.conf` and `kubelet.conf`) and a systemd service
57
-
(Kubernetes Kubelet):
81
+
.Example output
82
+
[source,terminal]
83
+
----
84
+
...
85
+
Degraded Machine Count: 0
86
+
Machine Count: 3
87
+
Observed Generation: 2
88
+
Ready Machine Count: 2
89
+
Unavailable Machine Count: 1
90
+
Updated Machine Count: 3
91
+
----
92
+
====
93
+
94
+
. To see each existing `MachineConfig` object, run the following command:
Note that the `MachineConfig` objects listed as `rendered` are not meant to be changed or deleted.
115
+
116
+
. To view the contents of a particular machine config (in this case, `01-master-kubelet`), run the following command:
58
117
+
59
118
[source,terminal]
60
119
----
61
120
$ oc describe machineconfigs 01-master-kubelet
121
+
----
122
+
+
123
+
The output from the command shows that this `MachineConfig` object contains both configuration files (`cloud.conf` and `kubelet.conf`) and a systemd service (Kubernetes Kubelet):
124
+
+
125
+
.Example output
126
+
[source,terminal]
127
+
----
62
128
Name: 01-master-kubelet
63
129
...
64
130
Spec:
@@ -89,7 +155,7 @@ ExecStart=/usr/bin/hyperkube \
89
155
--config=/etc/kubernetes/kubelet.conf \ ...
90
156
----
91
157
92
-
If something goes wrong with a machine config that you apply, you can always back out that change. For example, if you had run `oc create -f ./myconfig.yaml` to apply a machine config, you could remove that machine config by typing:
158
+
If something goes wrong with a machine config that you apply, you can always back out that change. For example, if you had run `oc create -f ./myconfig.yaml` to apply a machine config, you could remove that machine config by running the following command:
0 commit comments