Skip to content
Free since 2015. Built for the engineers who keep things running.

cat /articles/scheduling-the-removal-of-the-kube-proxy-ipvs-backend.md

Kubernetes

Scheduling the removal of the kube-proxy IPVS backend

Kubernetes SIG Network plans to remove the ipvs backend of kube-proxy in version 1.40, after deprecating it in 1.35, and urges users to move to nftables or iptables.

Kubernetes Blog16 Nov 2026 · 8 min read · summary

article --summary

The summary

The post explains that the ipvs kube-proxy backend, once added to fix iptables performance problems, never fully matched Kubernetes Service behavior and is now being retired. Kube-proxy's ipvs mode depends on iptables for some features and lacks batch updates, which limits its scaling and makes it hard to maintain. The post also notes that IPVS scheduler choices give little benefit here, because each node picks endpoints independently. Users on Kubernetes 1.36 or later with a kernel of 5.13 or newer are advised to switch to the nftables mode, which is feature-complete and performs about as well. Those who cannot switch can move to the improved iptables backend, and the post walks through how to change the kube-proxy configuration.

Editorial note: This is a summary of an article first published by Kubernetes Blog. The full piece is on their site.

Reading now

Topic
Kubernetes
Source
Kubernetes Blog
Published
16 Nov 2026
Format
Curated summary

Have a take on this?

Write it up and submit it. It goes on the list once an editor approves it.

Submit an article

articles --latest

Latest articles

New from the blogs we follow and the community.

All articles

newsletter --weekly

DevOps Weekly, minus the noise.

The best reads, new jobs and upcoming events, in one email a week.