Certified Kubernetes Administrator (CKA) Practice Test

The sequence of commands to mark a node as unavailable and reschedule all its pods involves first using the cordon command, followed by the drain command. Cordon prevents new pods from being scheduled on the node, effectively marking it as unschedulable. This is the first step to ensure that no new workloads are allocated to the node while it is being taken offline.

After cordoning the node, the drain command is used, which safely evicts all the pods from that node. It handles the rescheduling of pods by moving them to other available nodes, which is essential for maintaining application availability during maintenance or failure scenarios.

The third command in this sequence, get nodes, although it can be used to check the status of nodes, does not play a direct role in the process of making a node unavailable or rescheduling pods, hence, is not a critical step in the required actions.

This sequence effectively prepares the node for maintenance and ensures that workloads continue to run by moving them away from the now-unavailable node.