# Keepalived VIP for k8s

**URL:** <https://discuss.kubernetes.io/t/keepalived-vip-for-k8s/18880>\
**Category:** General Discussions\
**Tags:** development, network\
**Created:** [January 25, 2022, 11:47am UTC](https://discuss.kubernetes.io/t/keepalived-vip-for-k8s/18880 "2022-01-25T11:47:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wujl596](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/wujl596/32/9382_2.png) [@wujl596](https://discuss.kubernetes.io/u/wujl596)\
**Post date:** [January 25, 2022, 11:47am UTC](https://discuss.kubernetes.io/t/keepalived-vip-for-k8s/18880/1 "2022-01-25T11:47:52Z")

</div>

Asking for help? Comment out what you need so we can get more information to help you!

### Cluster information:

Kubernetes version:1.21.6  
Cloud being used: VPC  
Installation method:yum  
Host OS: centos7.9  
CNI and version:default  
CRI and version: defalut  
network plugin:flannel 0.15  
keepalived version:1.3.5  
kube-proxy mode:ipvs

I have a http service with nodePort 30080, i config keepalived VIP as :192.168.20.200/24 brd 192.168.20.255 dev eth0 label eth0:vip, when node is get VIP, but ipvsadm -ln | grep 30080, the 192.168.20.180 is not in the ipvs forward table, but the ipaddr for eth0 192.168.20.51/24 is in the ipvs table; if i change the VIP to 192.168.20.180/25(is not same to 24 well), it work correct, why? please help me, tks a lot.
