1. Testing the Full Bandwidth Start the iperf3 server on the target host 1 2 3 4 5 iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Test from the client host 1 iperf3 -c x.x.x.x -p 5201 -t 10 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Connecting to host x.

1. System Requirements Kubernetes, >= 1.16.0-0 Helm, >= 3.0 Linux kernel >= 4.9.17 For the process of upgrading the kernel on CentOS 7, see How to Switch the Data Plane to eBPF Under Calico. 2. Uninstalling Calico Delete the cluster resources 1 2 3 4 5 6 kubectl -n kube-system delete ds calico-node kubectl -n kube-system delete deploy calico-kube-controllers kubectl -n kube-system delete sa calico-node kubectl -n kube-system delete sa calico-kube-controllers kubectl -n kube-system delete cm calico-config kubectl -n kube-system delete secret calico-config 1 kubectl get crd | grep calico | awk '{print $1}' | xargs kubectl delete crd Bring down the Tunl0 interface 1 ifconfig tunl0 down Remove the Calico configuration files 1 rm -rf /etc/cni/net.

1. Environment Preparation 1.1 Calico eBPF Requirements System requirements Ubuntu 18.04.4+ Red Hat v8.2 Linux kernel v5.3+ If Calico does not detect a compatible kernel, it falls back to standard mode. Every node needs a BPF filesystem mounted at /sys/fs/bpf Calico version no lower than 3.13 1.2 Upgrading the Kernel This uses CentOS 7:

1. Calico 1.1 BIRD is not ready 1 kubectl -n kube-system get pod calico-node-xxx stays at 0/1 and never comes up, reporting calico/node is not ready: BIRD is not ready: BGP not established with Solution: Calico uses first-found by default, meaning it takes the NodeIP from the first NIC it finds.