When the k8s Service is configured with externalTrafficPolicy set to Local, the kube ip cloud provider assigns IP addresses in a pending state

[yomixvii]

kubectl get svc -n ingress-nginx

ingress-nginx ingress-nginx-controller LoadBalancer 10.11.164.75 80:31555/TCP,443:30455/TCP 4h23m

Service.yaml
... ...
type: LoadBalancer
loadBalancerIP: "10.1.2.46"
externalTrafficPolicy: Local
... ...

[yomixvii]

The version of k8s is v1.28.2

[lubronzhan]

Hi @yomixvii , kube-vip-cloud-provider sets the loadBalancerIP on the spec, then it's kube-vip's responsibility to assign that ip in status. You can file an issue in https://github.com/kube-vip/kube-vip/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen, with kube-vip's log.

BTW, to support externalTrafficlLocal, you need kube-vip with svc_enable flag set, and deployed on all of the nodes, so that it can monitor the pods on the same node