<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-d06lkxavg" -->

---
title: Scheduling the removal of the kube-proxy IPVS backend
description: Kubernetes SIG Network plans to remove the kube-proxy ipvs backend in Kubernetes 1.40, after deprecating it in 1.35. The ipvs backend solved iptables'...
canonical: https://daily.dev/posts/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-d06lkxavg
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Scheduling the removal of the kube-proxy IPVS backend | daily.dev
og:description: Kubernetes SIG Network plans to remove the kube-proxy ipvs backend in Kubernetes 1.40, after deprecating it in 1.35. The ipvs backend solved iptables'...
og:url: https://daily.dev/posts/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-d06lkxavg
og:image: https://api.daily.dev/og/posts/d06lKxavG.png
og:image:alt: Scheduling the removal of the kube-proxy IPVS backend
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Scheduling the removal of the kube-proxy IPVS backend

**[Kubernetes](https://daily.dev/sources/k8s)** · 8 min read · 1 upvotes · 0 comments

## Summary

Kubernetes SIG Network plans to remove the kube-proxy ipvs backend in Kubernetes 1.40, after deprecating it in 1.35. The ipvs backend solved iptables' performance problems but never reached full feature parity and has its own scaling issues since the kernel IPVS API lacks batch updates. Red Hat's plan to drop the iptables API from RHEL also threatens ipvs, which relies on iptables for some features. Users should migrate to nftables, GA since Kubernetes 1.33, or fall back to the now much-improved iptables backend.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://kubernetes.io/blog/2026/11/16/ipvs-removal>

## Questions this post answers

### When will Kubernetes remove the ipvs kube-proxy backend?

Kubernetes SIG Network plans to remove the ipvs kube-proxy backend in Kubernetes 1.40. It was officially deprecated as of Kubernetes 1.35, though it remains available with a deprecation warning until removal. Users running ipvs should migrate to either the nftables or iptables kube-proxy backends before then.

_Track the ipvs removal timeline on daily.dev so cluster upgrades don't break service proxying unexpectedly._

### Should I switch my kube-proxy ipvs clusters to nftables or iptables?

Switch to nftables if running Kubernetes 1.36 or later with a Linux kernel 5.13 or later, since nftables is feature-complete, fully supported, and has slightly better performance than ipvs. If nftables isn't available due to an older Kubernetes version or Linux distribution, the modern iptables backend is also a viable fallback after years of performance optimizations.

_Compare nftables and iptables kube-proxy tradeoffs on daily.dev before planning your cluster's migration path._

### Why is the kube-proxy ipvs backend being deprecated despite being faster?

The kernel IPVS API lacks batch update operations, so kube-proxy's ipvs backend can be slower than iptables when making many changes at once. It also never reached full feature parity with iptables, forced kube-proxy to fall back on iptables for some functionality, and faces a long-term support problem since Red Hat plans to remove the iptables API from RHEL entirely.

_Understand the ipvs tradeoffs on daily.dev before architecture decisions affect Kubernetes network performance._

## Similar posts on daily.dev

- [Isovalent Networking for Kubernetes 1.18: New Routing, Policy, and Observability Enhancements](https://daily.dev/posts/isovalent-networking-for-kubernetes-1-18-new-routing-policy-and-observability-enhancements-uehiidtza) · Isovalent · 1 upvotes · 0 comments
- [What to Expect From Kubernetes 1.36](https://daily.dev/posts/what-to-expect-from-kubernetes-1-36-u9p6lgf7l) · Cloud Native Now · 1 upvotes · 0 comments
- [Inside the Packet: How Kubernetes Networking Actually Works at L3/L4](https://daily.dev/posts/inside-the-packet-how-kubernetes-networking-actually-works-at-l3-l4-mlktkkrux) · Container Journal · 1 upvotes · 0 comments

---

Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#networking](https://daily.dev/tags/networking)

[View this post on daily.dev](https://daily.dev/posts/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-d06lkxavg)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Scheduling the removal of the kube-proxy IPVS backend","url":"https://daily.dev/posts/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-d06lkxavg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-d06lkxavg"},"datePublished":"2026-11-17T00:42:17.797Z","dateModified":"2026-11-17T00:53:10.647Z","description":"Kubernetes SIG Network plans to remove the kube-proxy ipvs backend in Kubernetes 1.40, after deprecating it in 1.35. The ipvs backend solved iptables'...","image":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","thumbnailUrl":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","isAccessibleForFree":true,"articleSection":"Kubernetes","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Kubernetes","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/k8s","url":"https://daily.dev/sources/k8s"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-d06lkxavg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,networking","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Kubernetes","item":"https://daily.dev/sources/k8s"},{"@type":"ListItem","position":3,"name":"Scheduling the removal of the kube-proxy IPVS backend"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-d06lkxavg#faq","mainEntity":[{"@type":"Question","name":"When will Kubernetes remove the ipvs kube-proxy backend?","acceptedAnswer":{"@type":"Answer","text":"Kubernetes SIG Network plans to remove the ipvs kube-proxy backend in Kubernetes 1.40. It was officially deprecated as of Kubernetes 1.35, though it remains available with a deprecation warning until removal. Users running ipvs should migrate to either the nftables or iptables kube-proxy backends before then. Track the ipvs removal timeline on daily.dev so cluster upgrades don't break service proxying unexpectedly."}},{"@type":"Question","name":"Should I switch my kube-proxy ipvs clusters to nftables or iptables?","acceptedAnswer":{"@type":"Answer","text":"Switch to nftables if running Kubernetes 1.36 or later with a Linux kernel 5.13 or later, since nftables is feature-complete, fully supported, and has slightly better performance than ipvs. If nftables isn't available due to an older Kubernetes version or Linux distribution, the modern iptables backend is also a viable fallback after years of performance optimizations. Compare nftables and iptables kube-proxy tradeoffs on daily.dev before planning your cluster's migration path."}},{"@type":"Question","name":"Why is the kube-proxy ipvs backend being deprecated despite being faster?","acceptedAnswer":{"@type":"Answer","text":"The kernel IPVS API lacks batch update operations, so kube-proxy's ipvs backend can be slower than iptables when making many changes at once. It also never reached full feature parity with iptables, forced kube-proxy to fall back on iptables for some functionality, and faces a long-term support problem since Red Hat plans to remove the iptables API from RHEL entirely. Understand the ipvs tradeoffs on daily.dev before architecture decisions affect Kubernetes network performance."}}]}
```

