A library cluster finished control-plane init and must add workers using the printed join instructions. What is the correct action on each worker?
Select an answer to reveal the explanation.
Short Explanation
Workers do not throw their own init party—they join the one already started. Use the kubeadm join line from init output (token plus CA hash) on each worker. A second init makes a splinter cluster, not a bigger library.
Full Explanation
After kubeadm init, additional nodes join with kubeadm join, targeting the control-plane endpoint and presenting a valid bootstrap token and discovery CA hash. Running init on workers creates separate clusters. Workers should not host the control-plane scheduler via admin.conf alone, and etcd data must not be mounted into ordinary Deployments for joining.