kind 环境做 cilium 完整的测试需要自己定制，有一定的复杂度。包括排查过程。
之前看 cilium labs， 看到应该是用 kind 环境起的，
然后 kube-ovn 也是用 kind 环境起的，
实际上有些配置参数的场景，确实需要定制。
默认的 kind 环境应该能做一部分，可能主要是 bpf 挂载那部分是异常的， 但是进而导致 cni channing 部署模式下的网络也是异常的
oot@debian:~/f/cilium vpc-ip-confilct-in-endpoint ✔ 19h47m
▶ k logs -f -n kube-system kube-ovn-cni-zptrd
Defaulted container "cni-server" out of: cni-server, hostpath-init (init), install-cni (init)
checking ovsdb-server status
checking ovs-vswitchd status
iptables v1.8.10 (legacy)
I0114 03:24:05.332475 4017 cniserver.go:33]
-------------------------------------------------------------------------------
Kube-OVN:
Version: v1.16.0
Build: 2026-01-13_20:58:55
Commit: git-83482958
Go Version: go1.25.5
Arch: amd64
-------------------------------------------------------------------------------
I0114 03:24:05.332568 4017 init.go:14] current capabilities: cap_chown,cap_dac_override,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_net_bind_service,cap_net_admin,cap_net_raw,cap_sys_chroot,cap_sys_ptrace,cap_sys_admin,cap_sys_nice,cap_mknod,cap_audit_write,cap_setfcap=ep
I0114 03:24:05.334836 4017 config.go:406] no --kubeconfig, use in-cluster kubernetes config
W0114 03:24:08.337151 4017 k8s.go:80] failed to dial apiserver "https://10.96.0.1:443": timed out dialing host "https://10.96.0.1:443"
W0114 03:24:11.337495 4017 k8s.go:80] failed to dial apiserver "https://10.96.0.1:443": timed out dialing host "https://10.96.0.1:443"
W0114 03:24:14.339793 4017 k8s.go:80] failed to dial apiserver "https://10.96.0.1:443": timed out dialing host "https://10.96.0.1:443"
W0114 03:24:17.341063 4017 k8s.go:80] failed to dial apiserver "https://10.96.0.1:443": timed out dialing host "https://10.96.0.1:443"
^C#
(v.v)
root@debian:~/f/cilium vpc-ip-confilct-in-endpoint ✔ 19h47m ⍉
▶
部署
root@debian:~/f/cilium vpc-ip-confilct-in-endpoint ✔ 19h47m ⍉
▶ kgn
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
kube-ovn-control-plane Ready control-plane 2m53s v1.35.0 172.18.0.2 <none> Debian GNU/Linux 12 (bookworm) 6.1.0-41-amd64 containerd://2.2.0
kube-ovn-worker Ready <none> 2m38s v1.35.0 172.18.0.3 <none> Debian GNU/Linux 12 (bookworm) 6.1.0-41-amd64 containerd://2.2.0
(v.v)
root@debian:~/f/cilium vpc-ip-confilct-in-endpoint ✔ 19h48m
▶ k get ds -A -o wide | grep cilium
kube-system cilium 2 2 2 2 2 kubernetes.io/os=linux 2m21s cilium-agent quay.io/cilium/cilium:v1.18.5 k8s-app=cilium
kube-system cilium-envoy 2 2 2 2 2 kubernetes.io/os=linux 2m21s cilium-envoy quay.io/cilium/cilium-envoy:v1.35.9-1767794330-db497dd19e346b39d81d7b5c0dedf6c812bcc5c9@sha256:81398e449f2d3d0a6a70527e4f641aaa685d3156bea0bb30712fae3fd8822b86 k8s-app=cilium-envoy
(v.v)
root@debian:~/f/cilium vpc-ip-confilct-in-endpoint ✔ 19h48m
▶ k get ds -A -o wide | grep ovn
kube-system kube-ovn-cni 2 2 0 2 0 kubernetes.io/os=linux 96s cni-server docker.io/kubeovn/kube-ovn:v1.16.0 app=kube-ovn-cni
kube-system ovs-ovn 2 2 2 2 2 kubernetes.io/os=linux 111s openvswitch docker.io/kubeovn/kube-ovn:v1.16.0 app=ovs
(v.v)
root@debian:~/f/cilium vpc-ip-confilct-in-endpoint ✔ 19h48m
▶
