Kubernetes SIG Network, the group that maintains the project's networking code, said in a blog post on November 16 that it plans to remove the ipvs backend from kube-proxy in Kubernetes 1.40. The backend has been deprecated since version 1.35. It still works today but prints a warning. kube-proxy is the component that routes traffic to services inside a cluster. The group tells all ipvs users to plan a move to the nftables or iptables backends.
The post gives reasons for the removal. The kernel IPVS interface fits the Kubernetes Services model poorly, and the backend never handled every edge case correctly. It is also costly to maintain. Red Hat plans to drop the iptables API from Red Hat Enterprise Linux, which would end ipvs mode there too. The post does not give a calendar date for version 1.40. It points readers to KEP-5495, the project's proposal document, for the full timeline.
For teams running ipvs, the post sets out a clear path. On Kubernetes 1.36 or later with Linux kernel 5.13 or later, the group recommends nftables, which it says performs slightly better than ipvs. Older setups can use iptables, which has improved since 2017. Either switch means changing the kube-proxy configuration. For iptables, the group advises rebooting each node. Teams have until 1.40 to finish.