🚨 Calico BGP 트러블 슈팅..

클러스터 Kubeadm init, join 후

Calico 설치시 발생한 문제이다.

 Warning  Unhealthy  16m   kubelet            Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused
  Warning  Unhealthy  16m   kubelet            Readiness probe failed: 2023-10-30 08:06:49.135 [INFO][215] confd/health.go 180: Number of node(s) with BGP peering established = 0
calico/node is not ready: BIRD is not ready: BGP not established with 172.31.16.104

---

Kubernetes 구성

https://nvtienanh.info/blog/cai-dat-kubernetes-cluster-tren-ubuntu-server-22-04

calico 의 cidr을 10.10.0.0/16으로 구성하였음.

처음에 문제가 뭔지 싶어서

해당 포스팅을 보고 방화벽 오픈이 필요하다고 해서 일단 포트를 개방함.
https://velog.io/@koo8624/Kubernetes-Calico-Error-caliconode-is-not-ready-BIRD-is-not-ready-BGP-not-established

네트워크 nic가 ec2인스턴스에 여러개 존재하는지 잘모르겠다..
그래도 혹시나 하는 마음에 nic를 지정할 수 있도록 daemonset의 변수를 수정하였음.
https://velog.io/@numerok/caliconode-is-not-ready-BIRD-is-not-ready-BGP-not-established-with

참고:
https://www.skyer9.pe.kr/wordpress/?p=7416

---

해결?

Bird Daemon 프로세스가 실행되지 않는 건가 싶어서
sudo systemctl status bird
sudo systemctl restart bird
명령어를 이용하여 버드를 확인하였음.

그러고 나섯 다시 kube-system 네임 스페이스의 컴포넌트들을 모두 확인해보니 ready 상태가 0/1에서 1/1로 바귀었다 (calico-node)

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  16m                default-scheduler  Successfully assigned kube-system/calico-node-5h5lb to ip-172-31-16-104
  Normal   Pulled     16m                kubelet            Container image "docker.io/calico/cni:v3.25.0" already present on machine
  Normal   Created    16m                kubelet            Created container upgrade-ipam
  Normal   Started    16m                kubelet            Started container upgrade-ipam
  Normal   Pulled     16m                kubelet            Container image "docker.io/calico/cni:v3.25.0" already present on machine
  Normal   Created    16m                kubelet            Created container install-cni
  Normal   Started    16m                kubelet            Started container install-cni
  Normal   Pulled     16m                kubelet            Container image "docker.io/calico/node:v3.25.0" already present on machine
  Normal   Created    16m                kubelet            Created container mount-bpffs
  Normal   Started    16m                kubelet            Started container mount-bpffs
  Normal   Pulled     16m                kubelet            Container image "docker.io/calico/node:v3.25.0" already present on machine
  Normal   Created    16m                kubelet            Created container calico-node
  Normal   Started    16m                kubelet            Started container calico-node
  Warning  Unhealthy  16m (x2 over 16m)  kubelet            Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused
  Warning  Unhealthy  16m                kubelet            Readiness probe failed: 2023-10-30 08:39:29.117 [INFO][218] confd/health.go 180: Number of node(s) with BGP peering established = 1
calico/node is not ready: BIRD is not ready: BGP not established with 172.31.7.96
  Warning  Unhealthy  16m  kubelet  Readiness probe failed: 2023-10-30 08:39:39.167 [INFO][239] confd/health.go 180: Number of node(s) with BGP peering established = 1
calico/node is not ready: BIRD is not ready: BGP not established with 172.31.31.33

describe 했을 때 여전히 이벤트에 에러 로그가 남아있지만 일단 정상 실행됨..