Lin Lin
Lin Lin
You'd better post it in English. The maintainers are all using English. I suggest you turn off the BGP of Calico to see if there is a conflict with kube-vip....
How did you start the static pod? `KUBERNETES_SERVICE_HOST` environment variable is only available for normal pods.
Event docker won't pull image automatically when running a container, why not pull the image at first?
The NET_ADMIN capacity can ensure the visibility of a network interface in the container. Can you create a static Pod to verify the problem of not seeing the WLAN Interface?...
Is there any plan to correct it? FYI, I can try if needed. @thebsdbox
You need to `git commit` with a `--signoff` to sign off the commit to avoid the DCO check failure. @jbguerraz
I think the yaml kube-vip generates is correct. In my k8s 1.24, the control plane node label key is "node-role.kubernetes.io/control-plane" which is the same as aforementioned. @alberk8 Would you share...
The key point you mssing I guess is that k8s service is done by kube-proxy, and kube-proxy is a DaemonSet. A DaemonSet pod can only be started when kubelet connected...
Yeah, kube-vip is designed for a production k8s cluster, not for microk8s, in which case you have only 1 k8s node(control-plane), HA won't be needed at all, right?
I think the key point you are confusing is that a LoadBalancer type Service in k8s need a external cloud provider which is implemented by kube-vip. Here is the document...