Before embarking on this journey, I want to make it clear that it might not be a smooth ride. kubeadm has a difficult task: It has to follow the evolution of Kubernetes itself, which is a moving target. As a result, it is not always stable. When I wrote the first edition of Mastering Kubernetes, I had to dig deep and hunt for various workarounds to make it work. Guess what? I had to do the same thing for the second edition. Be prepared to make some adjustments and ask around. If you want a more streamlined solution, I will discuss some very good options later.