when you say -
kubernetes cordons that node, meaning there will no new/existing pods scheduled on that node.
existing pods get evicted and move to other nodes.
$ k drain worker02 --ignore-daemonsets
node/worker02 already cordoned
WARNING: ignoring DaemonSet-managed Pods: kube-system/kube-proxy-x6trg, kube-system/weave-net-s2cg9
evicting pod default/testd-96769dccb-fqhxh
evicting pod default/testd-96769dccb-bg6p7
$ k get nodes
NAME STATUS ROLES AGE VERSION
master01 Ready control-plane,master 30d v1.21.0
worker01 Ready 29d v1.21.0
worker02 Ready,SchedulingDisabled 29d v1.21.0
$ k uncordon worker02
you can run k uncordon command to bring back the node. In one way cordon and uncordon are stop and start or restart of your node because everything running on the cordoned node gets evicted and created newly on other nodes.
$ which k
k: aliased to kubectl
hope this helps.