Live
Cloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AICloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AI
Kubernetes

Kubernetes 1.40 will drop the kube-proxy IPVS backend – migration guidance for engineers

AI SummaryPowered by AI

Kubernetes SIG Network announced that the IPVS mode of kube-proxy, deprecated in 1.35, will be removed in the 1.40 release. Practitioners must shift to the nftables or iptables backends to avoid service disruption and maintain performance.

The kube-proxy ipvs backend, first added as a performance experiment, is scheduled for removal in Kubernetes 1.40 after being deprecated in 1.35. Engineers who rely on this mode need to plan a migration to either the nftables or iptables backends to keep their clusters functional and performant.

Background: why the IPVS backend existed

Early versions of kube-proxy used iptables rules that grew linearly with the number of services. This caused two scaling issues: data‑plane latency, because each new connection traversed an O(n) rule set, and control‑plane latency, because any service or endpoint change triggered a full rewrite of the ruleset, consuming a full CPU core in large clusters. The ipvs backend leveraged the kernel IPVS subsystem’s hash tables to provide constant‑time lookups and avoided full rule‑set rewrites by updating individual entries via the IPVS API.

Why the IPVS backend is being retired

Despite its performance gains, the ipvs implementation never achieved full parity with iptables. Maintaining the code proved difficult after the original authors moved on, and the backend inherited several limitations:

  • It lacks batch‑update capabilities, making large‑scale changes slower than iptables in some scenarios.
  • To support advanced Service features, it falls back to iptables and ipset, re‑introducing the scaling problems it was meant to avoid.
  • Red Hat’s plan to drop the iptables API from RHEL means the ipvs backend would lose its underlying dependency on that platform.
These factors led SIG Network to deprecate the mode in v1.35 and schedule its removal in v1.40.

Operational implications and migration options

Practitioners should evaluate their current kube-proxy configuration. If --proxy-mode=ipvs is set, the cluster will emit a deprecation warning and will fail to start once v1.40 is adopted. Two supported alternatives exist:

  • nftables backend: Introduced experimentally in v1.29 and promoted to GA in v1.33, it offers a modern rule engine that replaces both iptables and ipvs. It eliminates the need for a separate iptables fallback and aligns with the kernel’s nftables subsystem.
  • iptables backend: The traditional mode remains fully supported. It continues to provide correct Service semantics, though large clusters may still experience the original scaling constraints.

Migration steps generally include updating the kube-proxy command line or ConfigMap to set --proxy-mode=nftables (or iptables), validating Service behavior in a staging environment, and monitoring CPU and latency metrics during the transition.

Related CloudNinjas coverage: Kubernetes.

What This Means For Practitioners

Teams should treat the upcoming removal as a hard deadline for any production workloads still using ipvs. The practical actions are:

  1. Audit clusters for the ipvs flag and document where it is used.
  2. Test the nftables backend in a non‑production cluster to confirm compatibility with existing Service configurations.
  3. If nftables is not viable, verify that the iptables backend meets performance expectations before the upgrade.
  4. Plan the kube-proxy configuration change to coincide with the next minor version upgrade that includes v1.40.

By completing these steps before the v1.40 release, engineers can avoid unexpected service outages and retain the performance characteristics they expect from their Kubernetes networking stack.

Originally published atKubernetes Blog