[TOC] calico 提供兩種方式安裝，分別是 `operator` 與 `manifest` 方法。這里只演示 `manifest` 方式卸載 # 卸載 ## 刪除 manifest 提供資源 ```shell $ kubectl delete -f calico.yaml secret "calico-etcd-secrets" deleted configmap "calico-config" deleted clusterrole.rbac.authorization.k8s.io "calico-kube-controllers" deleted clusterrolebinding.rbac.authorization.k8s.io "calico-kube-controllers" deleted clusterrole.rbac.authorization.k8s.io "calico-node" deleted clusterrolebinding.rbac.authorization.k8s.io "calico-node" deleted daemonset.apps "calico-node" deleted serviceaccount "calico-node" deleted deployment.apps "calico-kube-controllers" deleted serviceaccount "calico-kube-controllers" deleted poddisruptionbudget.policy "calico-kube-controllers" deleted ``` ## 清理環境 >[info] 集群所有節點都需要操作 ```shell # 刪除cni相關配置 $ rm -rf /etc/cni/net.d/ # 卸載ipip $ modprobe -r ipip # 清理bird協議的路由 $ ip route flush proto bird # 刪除calixxx網卡 $ ip link list | grep cali | awk '{print $2}' | cut -c 1-15 | xargs -I {} ip link delete {} # 刪除cali字符相關的iptables規則 # ## KUBE-相關的規則是kube-proxy生成的，之所以需要刪除它。因為 iptables-restore 拋出異常 Bad IP address "" 或者 Port '0' not valid 錯誤。所以直接將KUBE-相關規則刪除掉，使得kube-proxy重新生成規則(秒級別自動恢復/重啟kube-proxy) $ iptables-save | egrep -v "cali|KUBE-" | iptables-restore ``` # 驗證 ```shell # 檢查所有名字里面帶有 calico|tigera 的資源 $ kubectl get all --all-namespaces | egrep "calico|tigera" # 檢查所有名字里面帶有 calico|tigera 的 不帶namespace信息的 api resources $ kubectl api-resources --verbs=list -o name | egrep "calico|tigera" # 查看是否有cali或tunl0網卡 $ ip a | egrep "cali|tunl0" # 查看是否有bird協議的路由 $ ip route list proto bird # 查看是否有cali相關iptables規則 $ iptables-save | grep cali ``` > 如果 `api-resources` 資源有殘留的話，使用 `kubectl get crd -o name | egrep "calico|tigera" | xargs kubectl delete` 清理環境