報錯現象：
[root@k8s-node02 ~]# kubeadm join 192.168.43.12:6443 --token abcdef.0123456789abcdef \ > --discovery-token-ca-cert-hash sha256:ee53b0ba5728c73f989b4da3029cc75515e957cad8dc6772015c0920a901eddd [preflight] Running pre-flight checks [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/ error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables contents are not set to 1 [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` [root@k8s-node02 ~]#
解決辦法：
echo "1" >/proc/sys/net/bridge/bridge-nf-call-iptables #/pro的配置文件根據實際環境來
查看如下：
[root@k8s-node02 ~]# echo "1" >/proc/sys/net/bridge/bridge-nf-call-iptables [root@k8s-node02 ~]# kubeadm join 192.168.43.12:6443 --token abcdef.0123456789abcdef \ > --discovery-token-ca-cert-hash sha256:ee53b0ba5728c73f989b4da3029cc75515e957cad8dc6772015c0920a901eddd [preflight] Running pre-flight checks [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/ [preflight] Reading configuration from the cluster... [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml' [kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.14" ConfigMap in the kube-system namespace [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" [kubelet-start] Activating the kubelet service [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap... This node has joined the cluster: * Certificate signing request was sent to apiserver and a response was received. * The Kubelet was informed of the new secure connection details. Run 'kubectl get nodes' on the control-plane to see this node join the cluster. [root@k8s-node02 ~]#