Failed to Initialize the Kubernetes Cluster
Symptom
When the Kubernetes cluster initialization is performed on the primary node, "/proc/sys/net/bridge/bridge-nf-call-iptables contents are not set to 1" is reported.

Key Process and Cause Analysis
The value of /proc/sys/net/bridge/bridge-nf-call-iptables is incorrect.
Conclusion and Solution
- This file cannot be modified using the vim command. Run the following command to set this parameter to 1:
echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
- Check whether the value of /proc/sys/net/bridge/bridge-nf-call-iptables is 1.
cat /proc/sys/net/bridge/bridge-nf-call-iptables
- Initialize the Kubernetes cluster again.
Parent topic: Docker & Kubernetes