← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Kubernetes to Remove kube-proxy IPVS Backend in Version 1.40

🔄 Updated 4d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • IPVS backend deprecated in Kubernetes 1.35.
  • Removal scheduled for Kubernetes 1.40.
  • IPVS had performance benefits but lacked full feature parity.
  • Users should migrate to nftables or iptables backends.

Deprecation and Planned Removal

The Kubernetes SIG Network has announced the planned removal of the IPVS backend for kube-proxy in Kubernetes version 1.40. This follows its official deprecation in Kubernetes 1.35, where it remained available with a deprecation warning. The decision stems from the IPVS backend's complexity, incomplete feature set, and architectural differences that made it challenging to maintain compared to other backends.

Background of IPVS Backend

The IPVS backend was introduced as an experimental feature to improve performance over the iptables backend. It successfully addressed two main scaling issues: data plane latency, by reducing the O(n) rule matching for new connections, and control plane latency, by avoiding full iptables ruleset rewrites on every service or endpoint change. This significantly reduced CPU usage in large clusters that previously experienced 100% CPU utilization from iptables updates.

Challenges with IPVS

Despite its performance advantages, the kernel IPVS API proved to be a poor match for the Kubernetes Services API. This incompatibility prevented the IPVS backend from correctly implementing all edge cases of Kubernetes Service functionality, leading to its incomplete feature set. Its distinct architecture also increased maintenance overhead for the Kubernetes project.

Migration to nftables

The introduction of the nftables backend in Kubernetes 1.29, which became generally available in 1.33, was part of a strategy to replace both the iptables and IPVS backends. The nftables backend is intended to provide a more robust and maintainable solution. All current users of the IPVS backend are now advised to plan their migration to either the nftables or iptables backends before Kubernetes 1.40 is released.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Kubernetes SIG Network plans to remove the IPVS backend for kube-proxy in Kubernetes 1.40, following its deprecation in version 1.35. The IPVS backend, while offering performance improvements over iptables, proved difficult to maintain and was not fully feature-complete due to mismatches with the Kubernetes Services API. Users are advised to migrate to the nftables or iptables backends.