--- title: Linkerd Edge Release Roundup: September 2025 | daily.dev description: Recap of Linkerd's August 2025 edge releases (edge-25.8.1 through edge-25.8.5), all recommended for production use. Highlights include a fix for native-sidecar... canonical: https://daily.dev/posts/linkerd-edge-release-roundup-september-2025-vnet5ry5w twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Linkerd Edge Release Roundup: September 2025 | daily.dev og:description: Recap of Linkerd's August 2025 edge releases (edge-25.8.1 through edge-25.8.5), all recommended for production use. Highlights include a fix for native-sidecar... og:url: https://daily.dev/posts/linkerd-edge-release-roundup-september-2025-vnet5ry5w og:image: https://api.daily.dev/og/posts/vNEt5ry5w.png og:image:alt: Linkerd Edge Release Roundup: September 2025 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. # Linkerd Edge Release Roundup: September 2025 **[Linkerd](https://daily.dev/sources/linkerd)** · 4 min read · 0 upvotes · 0 comments ## Summary Recap of Linkerd's August 2025 edge releases (edge-25.8.1 through edge-25.8.5), all recommended for production use. Highlights include a fix for native-sidecar proxies landing in an error state, merging the policy-controller image into the main controller image (deprecating the policyController.image Helm value), switching the default iptables routing command from iptables-legacy to iptables-nft, dropping ARMv7 support, and the proxy defaulting to the post-quantum key exchange algorithm X25519MLKEM768. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did my Linkerd native-sidecar proxies end up in an error state after the main container exited? This was a bug introduced in edge-25.6.3 where native-sidecar proxies would land in an error state after the main container exited, tracked as issue #14289. It was fixed in edge-25.8.1, so anyone running edge-25.6.3 or later with native sidecars should upgrade to edge-25.8.1 or newer to resolve it. _daily.dev helps engineers running linkerd service mesh track fixes like this before they hit production._ ### Does Linkerd still ship a separate policy-controller image? No, as of edge-25.8.3 the policy controller is bundled into the main Linkerd controller image, and the separate policy-controller image is no longer shipped. This means the policyController.image Helm value is now ignored, reducing image pull traffic for Linkerd deployments. _Track breaking Helm value changes like this on daily.dev before upgrading your service mesh._ ### Why did Linkerd switch from iptables-legacy to iptables-nft by default? Linkerd switched the default command for programming routing tables from iptables-legacy to iptables-nft starting in edge-25.8.2. Nodes that do not support iptables-nft can revert by setting proxyInit.iptablesMode to legacy in the linkerd2-control-plane chart, or iptablesMode to legacy in the linkerd2-cni chart. _daily.dev keeps infrastructure teams current on networking defaults like linkerd's iptables switch._ ## Similar posts on daily.dev - [Linkerd 2.20, the Latest Release of the Cloud-Native Service Mesh, Arrives](https://daily.dev/posts/linkerd-2-20-the-latest-release-of-the-cloud-native-service-mesh-arrives-ketitd8if) · Cloud Native Now · 0 upvotes · 0 comments - [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 --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#infrastructure](https://daily.dev/tags/infrastructure), [#quantum-computing](https://daily.dev/tags/quantum-computing), [#service-mesh](https://daily.dev/tags/service-mesh) [View this post on daily.dev](https://daily.dev/posts/linkerd-edge-release-roundup-september-2025-vnet5ry5w) ```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":"Linkerd Edge Release Roundup: September 2025","url":"https://daily.dev/posts/linkerd-edge-release-roundup-september-2025-vnet5ry5w","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/linkerd-edge-release-roundup-september-2025-vnet5ry5w"},"datePublished":"2026-08-23T12:23:30.697Z","dateModified":"2026-08-23T12:56:07.484Z","description":"Recap of Linkerd's August 2025 edge releases (edge-25.8.1 through edge-25.8.5), all recommended for production use. Highlights include a fix for native-sidecar...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/30591c0cd239a67c0cfaf25acd299472?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/30591c0cd239a67c0cfaf25acd299472?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Linkerd","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":"Linkerd","logo":"https://media.daily.dev/image/upload/s--qmS-yPCD--/f_auto,q_auto/v1787487501/logos/linkerd?_a=BAMAMicg0","url":"https://daily.dev/sources/linkerd"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/linkerd-edge-release-roundup-september-2025-vnet5ry5w","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,infrastructure,quantum-computing,service-mesh","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Linkerd","item":"https://daily.dev/sources/linkerd"},{"@type":"ListItem","position":3,"name":"Linkerd Edge Release Roundup: September 2025"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/linkerd-edge-release-roundup-september-2025-vnet5ry5w#faq","mainEntity":[{"@type":"Question","name":"Why did my Linkerd native-sidecar proxies end up in an error state after the main container exited?","acceptedAnswer":{"@type":"Answer","text":"This was a bug introduced in edge-25.6.3 where native-sidecar proxies would land in an error state after the main container exited, tracked as issue #14289. It was fixed in edge-25.8.1, so anyone running edge-25.6.3 or later with native sidecars should upgrade to edge-25.8.1 or newer to resolve it. daily.dev helps engineers running linkerd service mesh track fixes like this before they hit production."}},{"@type":"Question","name":"Does Linkerd still ship a separate policy-controller image?","acceptedAnswer":{"@type":"Answer","text":"No, as of edge-25.8.3 the policy controller is bundled into the main Linkerd controller image, and the separate policy-controller image is no longer shipped. This means the policyController.image Helm value is now ignored, reducing image pull traffic for Linkerd deployments. Track breaking Helm value changes like this on daily.dev before upgrading your service mesh."}},{"@type":"Question","name":"Why did Linkerd switch from iptables-legacy to iptables-nft by default?","acceptedAnswer":{"@type":"Answer","text":"Linkerd switched the default command for programming routing tables from iptables-legacy to iptables-nft starting in edge-25.8.2. Nodes that do not support iptables-nft can revert by setting proxyInit.iptablesMode to legacy in the linkerd2-control-plane chart, or iptablesMode to legacy in the linkerd2-cni chart. daily.dev keeps infrastructure teams current on networking defaults like linkerd's iptables switch."}}]} ```