Transit platform ops must decommission a worker permanently. What clean removal sequence avoids stale node registrations?
Select an answer to reveal the explanation.
Short Explanation
Retiring a node isn’t just yanking the power cord—you empty it, check it out of inventory, and wipe the badge. Drain workloads, delete the Node object (and reset the host if it might rejoin), so the API doesn’t keep a ghost that looks like capacity. Stale nodes confuse monitoring and scheduling forever.
Full Explanation
Clean node removal drains workloads, then deletes the Node API object so the scheduler and controllers no longer treat the host as a member. On the host, kubeadm reset clears local cluster membership state if the machine might be reused. Leaving powered-off nodes registered creates stale inventory and misleading capacity signals.