Chapter 7: Deploying a Hybrid On-Premises Kubernetes Cluster

1. Use an internal NAT Hyper-V vSwitch if you plan to use the cluster for local development only. Any external inbound communication (apart from your Hyper-V host machine) will require NAT. Use an external Hyper-V vSwitch if your network has DHCP and DNS servers that you (or the network administrator) can manage. This will be the case in most production deployments.
2. In short, changing operating system configuration, such as disabling swap, installing a Docker container runtime, installing Kubernetes packages, and performing kubeadm init.
3. The Service subnet is a virtual subnet (non-routable) used by Pods for accessing services. Routable address translation from virtual IPs is performed by kube-proxy running on nodes. The Pod subnet is a global subnet used by all Pods in the cluster.
4. kubeadm token create --print-join-command...