Kubernetesでpodが起動しない_controllerがおかしい
node2がCrashLoopBackOffするのが治ったと思ったら今度は、controllerがおかしい
[root@master ~]# kubectl get pod -n metallb-system -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE controller-567586546b-dvn9b 0/1 ContainerCreating 0 28mnodelb speaker-6trpq 1/1 Running 0 28m 192.168.52.83 nodelb speaker-8rlqr 1/1 Running 0 28m 192.168.52.81 node1 speaker-rrg68 1/1 Running 0 28m 192.168.52.82 node2 [root@master ~]# [root@master ~]#
kubectl describe nodesでcontrollerの確認
Normal SandboxChanged 102s (x12 over 113s) kubelet, nodelb Pod sandbox changed, it will be killed and re-created. Warning FailedCreatePodSandBox 101s (x4 over 104s) kubelet, nodelb (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "352e9ae06a6fac420c26173d34e551323ba6d1a88a6073304ce7b2fe2a221f63" network for pod "controller-567586546b-dvn9b": NetworkPlugin cni failed to set up pod "controller-567586546b-dvn9b_metallb-system" network: failed to set bridge addr: "cni0" already has an IP address different from 10.244.2.1/24
failed to set bridge addr: "cni0" already has an IP address
IPをすでに持っていると、、
このエラー内容で検索
qiita.com
によると、以下コマンドで削除のflannel削除の必要あり。
ip link delete flannel.1 , ip link delete cni0
うまくいきました。
[root@master ~]# kubectl get pod -n metallb-system -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE controller-567586546b-vfkpg 1/1 Running 0 44s 10.244.2.98 nodelbspeaker-9fckf 1/1 Running 0 44s 192.168.52.82 node2 speaker-ckhjp 1/1 Running 0 44s 192.168.52.81 node1 speaker-z49bl 1/1 Running 0 44s 192.168.52.83 nodelb
bootcampできました。
ちょっと感動した。実はダッシュボードの設定とかうまくいってないので、もうちょっと頑張ります。。