# istio

Istio is an open, platform-independent service mesh that provides traffic management, policy enforcement, and telemetry collection.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Introducing Red Hat OpenShift Service Mesh 3.5

DevFeed: [Introducing Red Hat OpenShift Service Mesh 3.5](<https://devfeed.tech/articles/introducing-red-hat-openshift-service-mesh-3-5-135990.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/introducing-red-hat-openshift-service-mesh-35>)

Author: Jamie Longmuir

Published: 2026-11-16T00:00:00Z

Content type: release

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [istio](<https://devfeed.tech/topics/istio.md>), [SPIRE](<https://devfeed.tech/topics/spire.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-chatbot](<https://devfeed.tech/tags/ai-chatbot.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [ambient](<https://devfeed.tech/tags/ambient.md>), [dual-stack](<https://devfeed.tech/tags/dual-stack.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kiali](<https://devfeed.tech/tags/kiali.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [multicluster](<https://devfeed.tech/tags/multicluster.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>), [spire](<https://devfeed.tech/tags/spire.md>), [workload-identity](<https://devfeed.tech/tags/workload-identity.md>), [zero-trust](<https://devfeed.tech/tags/zero-trust.md>)

### AI overview

OpenShift Service Mesh 3.5 is generally available on OpenShift Container Platform 4.20 and later, including OpenShift 5.0. Based on Istio 1.31 and Kiali 2.33, it makes ambient-mode multiprimary multicluster and dual-stack IPv4/IPv6 generally available, and adds generally available SPIRE workload identity integration in sidecar mode, including federation; SPIRE is not yet supported in ambient mode. Sidecar-mode users can skip one Service Mesh minor release with revision-based upgrades, allowing workloads to jump two Service Mesh minor releases with one restart. Highlights include inherited mesh-wide resilience defaults, zone-aware load balancing, secure metrics scraping, and dynamic DNS for external HTTP destinations. Canary waypoint upgrades and standalone VM integration are Technology Preview; fleet management through Advanced Cluster Management is Developer Preview. Ambient multicluster currently supports multiprimary, multinetwork topology, while other topologies remain unsupported.

### Source excerpt

Red Hat OpenShift Service Mesh 3.5 is now generally available with Red Hat OpenShift Container Platform. Based on the Istio, Envoy, and Kiali projects, this release updates the version of Istio to 1.31 and Kiali to 2.33, and is supported on OpenShift Container Platform 4.20 and above, including Red Hat OpenShift 5.0. This release graduates multicluster with ambient mode, dual-stack IPv4/IPv6 with ambient mode, and Red Hat's zero trust workload identity manager (SPIRE) with sidecar mode to general availability, along with a substantial set of enhancements from Istio 1.31. Red Hat OpenShift 5.0

## Closing the Gap: Bringing Sidecar-Level Tracing to Istio's Ambient Mode with Kiali

DevFeed: [Closing the Gap: Bringing Sidecar-Level Tracing to Istio's Ambient Mode with Kiali](<https://devfeed.tech/articles/closing-the-gap-bringing-sidecar-level-tracing-to-istio-s-ambient-mode-with-kiali-100778.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/closing-the-gap-bringing-sidecar-level-tracing-to-istio-ambient-and-kiali/>)

Author: Josune Córdoba

Published: 2026-10-26T00:00:00Z

Content type: article

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [observability](<https://devfeed.tech/topics/observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [all](<https://devfeed.tech/tags/all.md>), [ambient](<https://devfeed.tech/tags/ambient.md>), [application](<https://devfeed.tech/tags/application.md>), [background](<https://devfeed.tech/tags/background.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [can](<https://devfeed.tech/tags/can.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [change](<https://devfeed.tech/tags/change.md>), [class](<https://devfeed.tech/tags/class.md>), [created](<https://devfeed.tech/tags/created.md>), [external](<https://devfeed.tech/tags/external.md>), [features](<https://devfeed.tech/tags/features.md>), [first](<https://devfeed.tech/tags/first.md>), [gap](<https://devfeed.tech/tags/gap.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kiali](<https://devfeed.tech/tags/kiali.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [observability](<https://devfeed.tech/tags/observability.md>), [services](<https://devfeed.tech/tags/services.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Istio 1.29 adds workload identity attributes that let Kiali Trace Overlay highlight the exact workload versions serving each hop, bringing ambient tracing to sidecar-level visibility alongside Kiali 2.25. In ambient mode, waypoint proxies provide Layer 7 telemetry; ztunnel operates at Layer 4 and cannot generate it. Trace identity evolved from waypoint naming in Istio 1.27 to destination-service attribution in 1.28-1.29 for OpenTelemetry, while Zipkin retained waypoint identity. Istio 1.30 represents both: span operation names reflect redirected service traffic, and infrastructure metadata identifies the waypoint. Kiali combines metrics-based graph topology with span attributes to map a selected trace onto services and workloads. Its Workload Details view can find traces associated with a workload's waypoint; `external_services.tracing.use_waypoint_name` can be set to `true` when identity mapping requires it.

### Source excerpt

Istio's ambient mode has steadily evolved across recent releases. Although it achieved GA in version 1.24, behavior has evolved as features have changed and stabilized in subsequent releases. With the release of Istio 1.29 and Kiali 2.25, we can now confidently state that tracing in ambient mode has reached full parity with sidecar mode. The Role of Waypoint Proxies As background, it is important to note that Layer 7 (L7) telemetry -- both metrics and traces -- is provided by waypoint proxies. Unlike sidecar mode, where the proxy resides within the same pod as the application, a waypoint is a shared, decoupled resource that can be scoped to a namespace, a service, or even specific workloads. It acts as the "gatekeeper" for the traffic it handles, processing all L7 logic. By contrast, the ambient node agent, ztunnel, only operates at Layer 4, and so cannot generate L7 telemetry. The Waypoint handling the traffic - view from Kiali's traffic graph The Shift in Identity: From Service to Waypoint Because waypoint proxies are external to the workload, identifying the "owner" of a trace has been an architectural challenge. In Istio 1.27, the waypoint proxy created the trace using the waypoint name as the service. Service traces with Istio 1.27 In Istio 1.28, a change was introduced to attribute the trace directly to the destination service, instead of the waypoint. This behavior remained through the 1.29 releases. Note that this shift was exclusive to the OpenTelemetry (OTel) provider; traditional formats like Zipkin continued to use the waypoint identity. Service traces with Istio 1.29 Istio 1.30 refined the situation by treating the waypoint as a "first-class citizen." The waypoint now preserves the architectural reality of the hop without obfuscating the destination. The operation name of the span correctly reflects the redirected service traffic, while the infrastructure metadata points to the waypoint. Service traces with Istio 1.30 The Missing Link: Workload Visibility

## Istio at KubeCon North America 2026: Let's Connect in Salt Lake City!

DevFeed: [Istio at KubeCon North America 2026: Let's Connect in Salt Lake City!](<https://devfeed.tech/articles/istio-at-kubecon-north-america-2026-let-s-connect-in-salt-lake-city-97276.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/kubecon-na/>)

Author: Francisco Herrera, for the Istio Community

Published: 2026-10-23T00:00:00Z

Content type: release

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Developer Events](<https://devfeed.tech/topics/developer-events.md>), [AI Networking](<https://devfeed.tech/topics/ai-networking.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ambient](<https://devfeed.tech/tags/ambient.md>), [ambient-mesh](<https://devfeed.tech/tags/ambient-mesh.md>), [cilium](<https://devfeed.tech/tags/cilium.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cloudnativecon](<https://devfeed.tech/tags/cloudnativecon.md>), [community](<https://devfeed.tech/tags/community.md>), [conference](<https://devfeed.tech/tags/conference.md>), [connect](<https://devfeed.tech/tags/connect.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [developing](<https://devfeed.tech/tags/developing.md>), [istio](<https://devfeed.tech/tags/istio.md>), [istio-day](<https://devfeed.tech/tags/istio-day.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [north-america](<https://devfeed.tech/tags/north-america.md>), [salt](<https://devfeed.tech/tags/salt.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

Istio's KubeCon + CloudNativeCon North America 2026 program in Salt Lake City includes an Istio Day on November 11 in the Cloud Native Theater, with sessions listed on AI-aware traffic management, multicluster discovery, mesh identity for AI agents, observability, and Ambient Mesh. Main conference sessions cover Istio with Cilium for multi-tenant network security, OTel aggregation at 10k-pod scale, and Envoy migration. A ContribFest invites newcomers to work with the Istio codebase, and an Istio kiosk offers opportunities to meet maintainers, contributors, and users. The supplied session list is incomplete.

### Source excerpt

Get ready for a packed agenda of Istio activities at KubeCon + CloudNativeCon North America 2026, including Istio Day sessions in the Cloud Native Theater on AI-aware traffic management, multicluster scalability, and agent identity, a ContribFest for new contributors, and chances to meet maintainers and fellow community members in person. Istio Day at Cloud Native Theater Join us at Istio Day on Wednesday, November 11 2026, part of the Cloud Native Theater at KubeCon + CloudNativeCon North America in Salt Lake City. Our hosts, Faseela K and Jackie Maertens, will open and close the day. These are the sessions lined up for the day: Istio at Scale: Lessons, Pitfalls, and Observability Unblocking Istio: Living Traffic Management Live! AI-Aware Traffic Management: Scaling Inference with Istio Ambient Mesh Two Namespaces, One Mesh: Zero-Downtime Releases for an Always-On Aviation Platform The Sidecar-to-Ambient Migration Nobody Warned Us About (AI Edition) Breaking the O(n²) Wall: Pub/Sub Federation for Istio Multicluster Service Discovery ServiceEntry Visibility: Tomorrow's ServiceEntry, Today Translating Mesh Identity into MCP Impersonation: Governing AI Agent Identities with Istio Istio at KubeCon Main Track ContribFest: Set Sail with Istio: Developing a Production Service Mesh, a perfect session for newcomers and aspiring contributors to jump into the codebase and community. Managing Network Security in Multi-Tenant Environments with Istio and Cilium Two-Stage OTel Aggregation: Taming Istio Cardinality at 10k-Pod Scale You don't have to migrate everything -- Envoy is the Bridge Between Your Old World and Your New One More Service Mesh Sessions We also recommend these sessions from the main conference with strong service mesh relevance: New Traffic, New Rules: Standardizing AI-Aware Networking in Kubernetes Will Your Gateway Leave You High and Dry? Feeling Lost? A Newcomer's Guide to the Gateway API From Bearer Tokens to Mesh-Native mTLS: Modernizing Service Identity at

## Istio 1.31 Adds Agentgateway Waypoints and Moves Release Artifacts off Google Cloud

DevFeed: [Istio 1.31 Adds Agentgateway Waypoints and Moves Release Artifacts off Google Cloud](<https://devfeed.tech/articles/istio-1-31-adds-agentgateway-waypoints-and-moves-release-artifacts-off-google-cloud-64344.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/istio-1-31-agentgateway/>)

Author: Mark Silvester

Published: 2026-10-03T08:30:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>)

Tags: [ambient-mesh](<https://devfeed.tech/tags/ambient-mesh.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [canary](<https://devfeed.tech/tags/canary.md>), [cloud-native-computing-foundation](<https://devfeed.tech/tags/cloud-native-computing-foundation.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [dns](<https://devfeed.tech/tags/dns.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [fips](<https://devfeed.tech/tags/fips.md>), [fips-140-3](<https://devfeed.tech/tags/fips-140-3.md>), [github](<https://devfeed.tech/tags/github.md>), [go](<https://devfeed.tech/tags/go.md>), [helm](<https://devfeed.tech/tags/helm.md>), [helm-charts](<https://devfeed.tech/tags/helm-charts.md>), [istio](<https://devfeed.tech/tags/istio.md>), [istio-1-31-agentgateway](<https://devfeed.tech/tags/istio-1-31-agentgateway.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [migration](<https://devfeed.tech/tags/migration.md>), [news](<https://devfeed.tech/tags/news.md>), [outage](<https://devfeed.tech/tags/outage.md>), [release](<https://devfeed.tech/tags/release.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [signing](<https://devfeed.tech/tags/signing.md>)

### AI overview

Istio 1.31 adds agentgateway waypoints for ambient meshes, alpha traffic shifting, and traffic management and security changes. The release also moves images and Helm charts off Google Cloud; affected teams need to migrate before scheduled outage tests and update signing-key handling.

### Source excerpt

Istio 1.31 adds agentgateway waypoints in ambient mode, with a canary configuration fix included in 1.31.1. It also ends the publication of images and Helm charts to Google Cloud, requiring repository migration ahead of the 13 October outage test and signing-key updates for teams verifying images. By Mark Silvester

## Retirement of Kubernetes integration jobs for unsupported Kubernetes versions

DevFeed: [Retirement of Kubernetes integration jobs for unsupported Kubernetes versions](<https://devfeed.tech/articles/retirement-of-kubernetes-integration-jobs-for-unsupported-kubernetes-versions-48817.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/retirement-of-k8s-integration-jobs/>)

Author: Francisco Herrera (Red Hat), Daniel Hawton (solo.io)

Published: 2026-09-16T00:00:00Z

Content type: release

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Script](<https://devfeed.tech/topics/script.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [end-of-life](<https://devfeed.tech/tags/end-of-life.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [retirement](<https://devfeed.tech/tags/retirement.md>), [services](<https://devfeed.tech/tags/services.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Istio is retiring CI integration tests for unsupported Kubernetes versions from Istio 1.32 onward. The change removes testing for older, end-of-life or soon-to-be unsupported Kubernetes releases and focuses CI resources on the supported range. Developers who still need older-version coverage can run the integration suite locally with kind.

### Source excerpt

The Istio Test and Release Working Group is retiring CI integration tests for older Kubernetes versions from the master branch, affecting Istio versions 1.32 and newer. What's changing Previously, Istio would have a supported range of Kubernetes versions that were typically N-3 or N-4 of the latest Kubernetes version, but would continue testing older Kubernetes versions. Currently, this means we are testing Kubernetes 1.23 through 1.36. With test-infra PR 6048, we are removing the tested older Kubernetes versions from testing, limiting our testing to only the supported Kubernetes range. This change is being made to the master branch, so will affect Istio versions 1.32 and forward. Why we're making this change These Kubernetes versions are either already end-of-life (EOL) or rapidly approaching it. Upstream Kubernetes supports minor releases for roughly 14 months; see the Kubernetes releases page for official support status. Maintaining old node images and running tests against EOL versions consumes valuable CI infrastructure and time. Retiring these jobs allows the working group to focus our testing resources on the actively supported versions that the vast majority of the community runs. What this means for you If you still need to test against these older versions, you can run the integration suite locally using kind. The integ-suite-kind.sh script is the exact entry point our CI uses. You can run it against the Kubernetes version you need by checking the test-infra commit history for the specific node image and configuration: $ prow/integ-suite-kind.sh \ --node-image kind-node-target-version \ --kind-config prow/config/mixedlb-service.yaml \ test.integration.kube Note: Replace the --node-image and --kind-config values with the versions previously used in CI for the Kubernetes version you want to test against. What's next You can always check the current set of tested Kubernetes versions for each Istio release in our support status table. If you have any questions

## Istio Project Announces 2026 Technical Oversight Committee Election Results

DevFeed: [Istio Project Announces 2026 Technical Oversight Committee Election Results](<https://devfeed.tech/articles/istio-project-announces-2026-technical-oversight-committee-election-results-48821.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/toc-election-results/>)

Author: Craig Box, for the Istio Steering Committee

Published: 2026-08-24T00:00:00Z

Content type: news

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Network](<https://devfeed.tech/topics/network.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Security](<https://devfeed.tech/topics/security.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ambient-mesh](<https://devfeed.tech/tags/ambient-mesh.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [community](<https://devfeed.tech/tags/community.md>), [election](<https://devfeed.tech/tags/election.md>), [governance](<https://devfeed.tech/tags/governance.md>), [istio](<https://devfeed.tech/tags/istio.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [networking](<https://devfeed.tech/tags/networking.md>), [performance](<https://devfeed.tech/tags/performance.md>), [security](<https://devfeed.tech/tags/security.md>), [services](<https://devfeed.tech/tags/services.md>), [technical-leadership](<https://devfeed.tech/tags/technical-leadership.md>), [toc](<https://devfeed.tech/tags/toc.md>)

### AI overview

The Istio project announces the results of its 2026 Technical Oversight Committee election. Three incumbent members were re-elected to two-year terms, providing continuity for the project's technical leadership and ongoing development of ambient mesh for cloud-native networking.

### Source excerpt

Under the governance system introduced in 2024 for the Technical Oversight Committee (TOC), the Istio project holds annual elections for three of the six seats. This ensures continuous technical leadership while maintaining community-driven momentum. This year's election saw four candidates stand for the three available two-year terms. Following the conclusion of the voting process by the Steering Committee, we are pleased to announce that three incumbents have been re-elected to serve another term on the Istio TOC: Keith Mattix John Howard Mitch Connors Each of these returning members has contributed significantly to the architectural direction, security model, and performance of Istio. Their ongoing tenure provides valuable continuity as the project continues to advance ambient mesh as the standard for cloud native networking. We extend our sincere gratitude to all four candidates who stepped forward. Having competitive elections with strong nominees across the community reflects the health, active engagement, and collaborative spirit of the Istio ecosystem. On behalf of the entire Istio community, the Steering Committee congratulates our re-elected TOC members and thanks everyone who participated in the nomination and voting process.

## An Update on Our Container Registry Migration

DevFeed: [An Update on Our Container Registry Migration](<https://devfeed.tech/articles/an-update-on-our-container-registry-migration-48815.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/retirement-of-gcr.io-follow-up/>)

Author: Steven Jin (Microsoft)

Published: 2026-07-23T00:00:00Z

Content type: release

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>), [container](<https://devfeed.tech/topics/container.md>), [migration](<https://devfeed.tech/topics/migration.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [container-registry](<https://devfeed.tech/tags/container-registry.md>), [containers](<https://devfeed.tech/tags/containers.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [migration](<https://devfeed.tech/tags/migration.md>), [services](<https://devfeed.tech/tags/services.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

Istio announces that it will retire the registry.istio.io/release container registry in late 2026 because Cloudflare proxy traffic triggers rate limits on free hosting platforms. Users are advised to migrate to docker.io/istio and consider a pull-through cache.

### Source excerpt

In a previous blog post, we announced that Istio will retire the gcr.io/istio-release container registry in late 2026 and switch to registry.istio.io/release as the new home for Istio images. The original design was that registry.istio.io/release would be a Cloudflare worker that proxied requests to any OCI-compliant registry, allowing us to switch registries without any interruption to Istio users. Currently, we proxy to gcr.io/istio-release. As mentioned before, we are retiring gcr.io/istio-release in late 2026. With a limited infrastructure budget for 2027, we plan to use free container hosting platforms to host Istio images. Unfortunately, proxying through Cloudflare means that we funnel all traffic through a few egress IPs, triggering rate-limiting policies on free container hosting platforms. After discussions with hosting platforms regarding this limitation, we have made the difficult decision to retire registry.istio.io/release. We will keep hosting registry.istio.io/release until late 2026. As always, we will publish Istio images to docker.io/istio and plan on publishing to mirrors in the future. Am I affected? By default, Istio 1.30 installations use registry.istio.io/release as their container registry. All other Istio versions default to docker.io/istio. You can check whether you are affected by running the following: $ kubectl get pods --all-namespaces -o json \ | jq -r '.items[] | select(.spec.containers[].image | startswith("registry.istio.io/release")) | "\(.metadata.namespace)/\(.metadata.name)"' The above command will list all the pods that use images hosted on registry.istio.io/release. If there are any such pods, you will likely need to migrate. Note that we will still retire gcr.io/istio-release in late 2026 as mentioned in the previous post, so you should check for gcr.io/istio-release usage too. What to do today Although we plan to keep images available on registry.istio.io/release and gcr.io/istio-release until late 2026, we suggest you migra

## Hardening Kubernetes Security with Istio Ambient Mode on Flat Networks

DevFeed: [Hardening Kubernetes Security with Istio Ambient Mode on Flat Networks](<https://devfeed.tech/articles/hardening-kubernetes-security-with-istio-ambient-mode-on-flat-networks-48812.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/istio-network-security-flat-networks-ambient-mode/>)

Author: Harshwardhan Mehrotra - One2N

Published: 2026-06-20T00:00:00Z

Content type: article

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Security](<https://devfeed.tech/topics/security.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Network Segmentation](<https://devfeed.tech/topics/network-segmentation.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>)

Tags: [ambient](<https://devfeed.tech/tags/ambient.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [bare-metal](<https://devfeed.tech/tags/bare-metal.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-security](<https://devfeed.tech/tags/kubernetes-security.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [mutual-tls](<https://devfeed.tech/tags/mutual-tls.md>), [network-segmentation](<https://devfeed.tech/tags/network-segmentation.md>), [networks](<https://devfeed.tech/tags/networks.md>), [on-prem](<https://devfeed.tech/tags/on-prem.md>), [security](<https://devfeed.tech/tags/security.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

This article explains how Istio Ambient Mode can provide workload-level isolation and security for Kubernetes workloads on flat on-premises networks. It discusses using the service mesh for zero-trust identity, automatic mTLS encryption, and service observability, including in hybrid EKS deployments.

### Source excerpt

If you've moved a workload off AWS and onto on-prem infrastructure, you've likely run into this: the network isolation you got for free on the cloud does not exist on bare metal. On AWS, Security Groups and VPC boundaries enforce service boundaries quietly in the background. Most teams never have to think about it. On-prem, the network is flat by default. Your payment service, your internal admin panel, your logging agent, and your customer-facing API all sit in the same cluster with nothing between them at the network layer. You can get that isolation back through firewall rules and network segmentation, but on most on-prem setups that means working through infra teams with their own change management cycles. When you are mid-migration and trying to move fast, that is a meaningful constraint. So, on an EKS Hybrid deployment that we were running, we decided to solve this at the mesh layer instead. We already had Istio in the stack, and it gave us a way to enforce workload-level isolation without waiting for network-level changes. The security team reviewed the model and signed off, because the controls we built mapped directly to what they would have required from the firewall anyway. This talk covers the broader EKS Hybrid setup if you want that context. This post is about how we built that isolation layer, layer by layer, and what we learned doing it. Why Istio (even for small clusters) You don't need a massive microservices architecture to benefit from Istio. Even in a small cluster, the mesh gives you three things that are hard to get any other way: Zero-Trust Identity: Instead of trusting a service because it has a certain IP address, you trust it because it holds a cryptographically verified certificate tied to its identity. An attacker who gets onto the network cannot fake that. Transparent Encryption: All traffic between services is encrypted automatically using mTLS (mutual TLS, meaning both sides verify each other), with no changes needed to your applicati

## Introducing the TrafficExtension API

DevFeed: [Introducing the TrafficExtension API](<https://devfeed.tech/articles/introducing-the-trafficextension-api-48822.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/traffic-extension-api/>)

Author: Liam White - Docusign

Published: 2026-05-18T00:00:00Z

Content type: release

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [API](<https://devfeed.tech/topics/api.md>), [Lua](<https://devfeed.tech/topics/lua.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [container](<https://devfeed.tech/topics/container.md>)

Tags: [ambient](<https://devfeed.tech/tags/ambient.md>), [api](<https://devfeed.tech/tags/api.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [extensibility](<https://devfeed.tech/tags/extensibility.md>), [extension](<https://devfeed.tech/tags/extension.md>), [go](<https://devfeed.tech/tags/go.md>), [http](<https://devfeed.tech/tags/http.md>), [istio](<https://devfeed.tech/tags/istio.md>), [logging](<https://devfeed.tech/tags/logging.md>), [lua](<https://devfeed.tech/tags/lua.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [oci](<https://devfeed.tech/tags/oci.md>), [payload](<https://devfeed.tech/tags/payload.md>), [policy-enforcement](<https://devfeed.tech/tags/policy-enforcement.md>), [rust](<https://devfeed.tech/tags/rust.md>), [services](<https://devfeed.tech/tags/services.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traffic-extension](<https://devfeed.tech/tags/traffic-extension.md>), [wasm](<https://devfeed.tech/tags/wasm.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Istio 1.30 introduces TrafficExtension, a unified API for configuring Lua scripts and WebAssembly plugins in Envoy-based sidecars, gateways, and waypoints. The API replaces WasmPlugin as the primary proxy extensibility mechanism and supports HTTP and TCP traffic, with extensions for tasks such as authentication, logging, telemetry, policy enforcement, and request or response transformation.

### Source excerpt

Mesh extensibility has always been a core tenet of Istio's design. By allowing users to inject custom logic directly into the data plane, Istio enables a wide range of use cases for performing custom authentication, collecting specialized telemetry, or transforming requests and responses on-the-fly. Until now Istio's only supported extensibility API was WasmPlugin, which served WebAssembly-based extensions. Users who wanted to leverage Lua scripts could only do so indirectly via EnvoyFilter, a low-level mechanism that is powerful but easy to misconfigure. Istio 1.30 introduces the TrafficExtension API -- a single, unified API for configuring Wasm and Lua extensions for Envoy-based sidecars, gateways and waypoints. What is TrafficExtension? TrafficExtension is a new Istio API that replaces WasmPlugin as the primary proxy extensibility mechanism. It supports two extension types: Lua scripts -- inline Lua scripts embedded directly in the resource, executed within Envoy with no module distribution required. Best for simple header manipulation, logging, and conditional logic. Applied to Layer 7 (HTTP) traffic only. WebAssembly plugins -- Proxy-Wasm sandbox modules loaded dynamically from OCI image registries. Supports multiple languages (Go, Rust, C++, AssemblyScript) and is recommended for complex processing, policy enforcement, telemetry collection, and payload mutations. Applied to Layer 7 (HTTP) or layer 4 (TCP) traffic. See the TrafficExtension concepts page for detailed guidance on choosing between Lua and Wasm for your use case. Writing extensions Lua Lua scripts are written inline. The following example reads an x-number request header, computes whether the value is even or odd, and adds an x-parity response header: apiVersion: extensions.istio.io/v1alpha1 kind: TrafficExtension metadata: name: parity namespace: istio-system spec: selector: matchLabels: istio: ingressgateway lua: inlineCode: | function envoy_on_request(request_handle) local number = tonumber(request

## Kubeflow Community Distribution 26.03.1 Release Announcement

DevFeed: [Kubeflow Community Distribution 26.03.1 Release Announcement](<https://devfeed.tech/articles/kubeflow-community-distribution-26-03-1-release-announcement-17609.md>)

Original publisher: [Read original article](<https://blog.kubeflow.org/kubeflow-26.03-release/>)

Author: Kubeflow 26.03 Release Team

Published: 2026-04-11T05:00:00Z

Content type: release

Language: en

Sources: [Kubeflow](<https://devfeed.tech/sources/kubeflow.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [MinIO](<https://devfeed.tech/topics/minio.md>), [istio](<https://devfeed.tech/topics/istio.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [ci](<https://devfeed.tech/tags/ci.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [minio](<https://devfeed.tech/tags/minio.md>), [network](<https://devfeed.tech/tags/network.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [release](<https://devfeed.tech/tags/release.md>), [storage](<https://devfeed.tech/tags/storage.md>), [ui](<https://devfeed.tech/tags/ui.md>), [updates](<https://devfeed.tech/tags/updates.md>), [versioning](<https://devfeed.tech/tags/versioning.md>)

### AI overview

The Kubeflow Community Distribution 26.03.1 release introduces calendar-based versioning and updates components including Kubernetes, Kubeflow Pipelines, KServe, Trainer, notebooks, the dashboard, Istio, and related dependencies. It also adds native OIDC support, conditional and parallel Local Runner control flows, SeaweedFS storage support, and completes MinIO deprecation.

### Source excerpt

The release versioning is now calendar-based (Year.Month.Patch). Around two base releases are planned per year with optional patch releases. The best-effort only community support is roughly 6 months and there is commercial support available from multiple vendors. Please update regularly as explained in our upgrading and extending section to benefit also from security and performance improvements. Release details: 26.03 and 26.03.1.

## Simplifying Egress Routing to Wildcard Destinations

DevFeed: [Simplifying Egress Routing to Wildcard Destinations](<https://devfeed.tech/articles/simplifying-egress-routing-to-wildcard-destinations-48811.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/egress-dynamic-dns/>)

Author: Rudrakh Panigrahi (Salesforce)

Published: 2026-04-09T00:00:00Z

Content type: article

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [TLS handshake](<https://devfeed.tech/topics/tls-handshake.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [gateway](<https://devfeed.tech/topics/gateway.md>), [Network](<https://devfeed.tech/topics/network.md>), [proxy](<https://devfeed.tech/topics/proxy.md>)

Tags: [ambient](<https://devfeed.tech/tags/ambient.md>), [egress](<https://devfeed.tech/tags/egress.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [istio](<https://devfeed.tech/tags/istio.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [networking](<https://devfeed.tech/tags/networking.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [routing](<https://devfeed.tech/tags/routing.md>), [service-entry](<https://devfeed.tech/tags/service-entry.md>), [services](<https://devfeed.tech/tags/services.md>), [tls](<https://devfeed.tech/tags/tls.md>), [tls-handshake](<https://devfeed.tech/tags/tls-handshake.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [traffic-management](<https://devfeed.tech/tags/traffic-management.md>), [waypoint](<https://devfeed.tech/tags/waypoint.md>), [wildcard](<https://devfeed.tech/tags/wildcard.md>)

### AI overview

This article explains Istio support for wildcard ServiceEntry resources with DYNAMIC_DNS resolution. The feature lets sidecars route HTTPS traffic to wildcard destinations while reducing the need to register dynamic subdomains individually. It also describes the earlier egress-gateway and SNI-based approach.

### Source excerpt

Overview Controlling egress traffic is a common requirement in service mesh deployments. Many organizations configure their mesh to allow only explicitly registered external services by setting: meshConfig.outboundTrafficPolicy.mode = REGISTRY_ONLY With this configuration, any external destination must be registered in the mesh using resources such as ServiceEntry with fully qualified domain names and a DNS resolution type. apiVersion: networking.istio.io/v1 kind: ServiceEntry metadata: name: external-wikipedia-https namespace: istio-system spec: hosts: - "www.wikipedia.org" ports: - name: tls number: 443 protocol: TLS location: MESH_EXTERNAL resolution: DNS exportTo: - "*" However, some external services expose many dynamic subdomains where applications may need to access endpoints such as: https://en.wikipedia.org https://de.wikipedia.org https://upload.wikipedia.org As the list of hostnames grows, registering each one individually quickly becomes impractical to manage and scale. To address this, Istio needs support for wildcard hostname registration. Why wildcard HTTPS egress is difficult When a workload initiates an HTTPS connection, the destination hostname is transmitted in the TLS handshake via the Server Name Indication (SNI) field. For example, a client calling https://en.wikipedia.org sends the hostname en.wikipedia.org in the ClientHello SNI field during the TLS handshake. Istio sidecars intercept outbound connections and determine whether the destination is registered and how it should be routed. However, Istio's routing model normally requires the upstream destination to be known ahead of time. Even if a wildcard match is used in routing rules, the final upstream cluster must still correspond to a statically configured service. Because different subdomains may resolve to different endpoints, routing directly to wildcard hosts was historically not straightforward. SNI routing via Egress Gateway This problem was previously addressed in the Istio blog post

## Istio Project Announces 2026 Steering Committee

DevFeed: [Istio Project Announces 2026 Steering Committee](<https://devfeed.tech/articles/istio-project-announces-2026-steering-committee-48819.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/steering-election-results/>)

Author: Ram Vennam, for the Istio Steering Committee

Published: 2026-03-27T00:00:00Z

Content type: news

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [community](<https://devfeed.tech/tags/community.md>), [election](<https://devfeed.tech/tags/election.md>), [governance](<https://devfeed.tech/tags/governance.md>), [istio](<https://devfeed.tech/tags/istio.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [services](<https://devfeed.tech/tags/services.md>), [steering](<https://devfeed.tech/tags/steering.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

The Istio Project announces the results of its 2026 Steering Committee elections and names the nine Contribution Seat holders. The new committee will serve for one year.

### Source excerpt

The Istio Steering Committee oversees the administrative aspects of the project, including governance, branding, marketing, and working with the CNCF. Every year, we estimate the proportion of the hundreds of companies that have contributed to Istio in the past year, and use that metric to proportionally allocate the nine Contribution Seats on our Steering Committee. After that, four Community Seats are voted for by our project members, with candidates being from companies that did not receive Contribution Seats. In February, we announced the Contribution Seat allocation, and invited candidates to stand for the Community Seat elections. As the election officer, I am pleased to announce the results of that election, as well as the individuals who will represent the top contributors. Community Seats Five candidates stood for our four open seats. Using Condorcet-method ranked voting, the following four candidates have been elected: Faseela K, Ericsson Software Technology Craig Box, Independent Tyler Schade, GEICO Tech Zhonghu Xu, Huawei We're excited to welcome this fantastic group of community leaders. Faseela is returning for her fourth term on Steering and also serves on the CNCF Technical Oversight Committee. Craig has been on the Steering Committee since 2020 and recently ended his term as the maintainer representative on the CNCF Governing Board. Tyler is a new face on Steering, bringing an end-user perspective from GEICO Tech, where he leads a team building a custom service mesh on Istio. Zhonghu has been an Istio contributor since the project's early days, is a core maintainer in multiple working groups, and is transitioning this year from a Contribution Seat to a Community Seat. Contribution Seats Our supporting companies have made their choices for the nine Contribution Seats. They will be held by: Zack Butcher (Tetrate) Rob Cernich (Red Hat) John Howard (Solo.io) Steven Jin Xuan (Microsoft) Jack Ma (Microsoft) Keith Mattix (Microsoft) Louis Ryan (Solo.io) Li

## Istio is Migrating Container Registries

DevFeed: [Istio is Migrating Container Registries](<https://devfeed.tech/articles/istio-is-migrating-container-registries-48816.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/retirement-of-gcr.io/>)

Author: Steven Jin (Microsoft), John Howard (Solo.io)

Published: 2026-03-23T00:00:00Z

Content type: article

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [migration](<https://devfeed.tech/topics/migration.md>), [container](<https://devfeed.tech/topics/container.md>), [Helm charts](<https://devfeed.tech/topics/helm-charts.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [container](<https://devfeed.tech/tags/container.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [helm](<https://devfeed.tech/tags/helm.md>), [helm-charts](<https://devfeed.tech/tags/helm-charts.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [migration](<https://devfeed.tech/tags/migration.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

Istio is moving its container images from gcr.io/istio-release as part of a broader migration away from Google Cloud. The post explains how to identify affected clusters and update istioctl, Helm, and private-registry configurations to use the new registry.istio.io location before the old registry is retired on January 1, 2027.

### Source excerpt

The information in this post has been updated. See An Update on Our Container Registry Migration for the latest guidance. Due to changes in Istio's funding model, Istio images will no longer be available at gcr.io/istio-release starting January 1st, 2027. That is, clusters that reference images hosted on gcr.io/istio-release might fail to create new pods in 2027. In fact, we are fully migrating all Istio artifacts out of Google Cloud, including Helm charts. Future communications will cover the migration of Helm charts and other artifacts. This post will focus on what you can do today in response to the 2027 container registry migration. Am I affected? By default, Istio installations use Docker Hub (docker.io/istio) as their container registry, but many users choose to use the gcr.io/istio-release mirror. You can check whether you are using the mirror using the following command. $ kubectl get pods --all-namespaces -o json \ | jq -r '.items[] | select(.spec.containers[].image | startswith("gcr.io/istio-release")) | "\(.metadata.namespace)/\(.metadata.name)"' The above command will list all the pods that use images hosted on gcr.io/istio-release. If there are any such pods, you will likely need to migrate. Even if you are using Docker Hub as your registry, we suggest that you migrate to registry.istio.io in case Istio images are no longer available on Docker Hub in the future. See below for more details. What to do today Although we plan to keep images available on gcr.io/istio-release until late 2026, we have set up registry.istio.io as the new home for Istio images. Please migrate to using registry.istio.io as soon as possible. Using istioctl If you install Istio using istioctl, you can update your IstioOperator configuration as follows: # istiooperator.yaml apiVersion: install.istio.io/v1alpha1 kind: IstioOperator spec: # ... hub: registry.istio.io/release # Everything else can stay the same unless you reference `gcr.io/istio-release` images elsewhere and install I

## Security Considerations on Istio's CRDs with Namespace-based Multi-Tenancy

DevFeed: [Security Considerations on Istio's CRDs with Namespace-based Multi-Tenancy](<https://devfeed.tech/articles/security-considerations-on-istio-s-crds-with-namespace-based-multi-tenancy-48818.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/security-considerations-on-namespace-based-multi-tenancy/>)

Author: Lorin Lehawany - ERNW, Sven Nobis - ERNW

Published: 2026-03-21T00:00:00Z

Content type: article

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Multi-tenancy](<https://devfeed.tech/topics/multi-tenancy.md>), [Security](<https://devfeed.tech/topics/security.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [istio](<https://devfeed.tech/tags/istio.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [man-in-the-middle](<https://devfeed.tech/tags/man-in-the-middle.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [mitm](<https://devfeed.tech/tags/mitm.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [routing](<https://devfeed.tech/tags/routing.md>), [security](<https://devfeed.tech/tags/security.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [services](<https://devfeed.tech/tags/services.md>), [traffic-management](<https://devfeed.tech/tags/traffic-management.md>)

### AI overview

This article examines a possible man-in-the-middle attack in namespace-based multi-tenant Istio deployments. It explains how Istio traffic-routing resources can redirect or intercept traffic across namespaces and discusses the risks and mitigation considerations for shared meshes, including multi-cluster deployments.

### Source excerpt

The Istio project wants to address a possible Man-in-the-Middle (MITM) attack scenario in which a VirtualService can redirect or intercept traffic within the service mesh. This affects namespace-based multi-tenancy clusters where tenants have the permissions to deploy Istio resources (networking.istio.io/v1). This blog post highlights the risks of using Istio in multi-tenant clusters and explains how users can mitigate these risks and safely operate Istio in their deployments. Please note that the issues even extend beyond the cluster scope in a "single mesh with multiple clusters" deployment. The behavior described in this post applies to Istio version 1.29.0 and to all versions since the introduction of the mesh gateway option in the VirtualService resource. Background Namespace-based Multi-Tenancy Namespaces in Kubernetes provide a mechanism for organizing groups of resources within a cluster. Namespaces provide a logical abstraction that allows teams, applications, or environments to share a single cluster while isolating their resources via controls such as Network Policies, RBAC, and so on. In this blog post, we focus on running Istio in clusters where multiple tenants share the same cluster and service mesh, and can deploy Istio resources (networking.istio.io/v1) in their namespaces while relying on namespace boundaries for isolation. Traffic Routing in Istio Istio provides traffic management capabilities by separating application logic from network routing behavior. It introduces additional configuration resources through CRDs that allow operators to define how traffic should be routed between services in the mesh. One of the central resources for this purpose is the VirtualService. A VirtualService defines a set of routing rules that determine how requests to hosts specified in spec.hosts.[] are handled. These rules can match requests based on properties such as HTTP headers, paths, or ports, and can then direct the traffic to one or more destination servic

## Istio at KubeCon Europe 2026: Let's Connect in Amsterdam!

DevFeed: [Istio at KubeCon Europe 2026: Let's Connect in Amsterdam!](<https://devfeed.tech/articles/istio-at-kubecon-europe-2026-let-s-connect-in-amsterdam-48813.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/kubecon-eu/>)

Author: Francisco Herrera, for the Istio Community

Published: 2026-02-23T00:00:00Z

Content type: article

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [ingress-nginx](<https://devfeed.tech/topics/ingress-nginx.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [model-serving](<https://devfeed.tech/topics/model-serving.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ambient-mesh](<https://devfeed.tech/tags/ambient-mesh.md>), [cloudnativecon](<https://devfeed.tech/tags/cloudnativecon.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [conference](<https://devfeed.tech/tags/conference.md>), [inference](<https://devfeed.tech/tags/inference.md>), [ingress-nginx](<https://devfeed.tech/tags/ingress-nginx.md>), [istio](<https://devfeed.tech/tags/istio.md>), [istio-day](<https://devfeed.tech/tags/istio-day.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [migration](<https://devfeed.tech/tags/migration.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

Istio's agenda for KubeCon + CloudNativeCon Europe 2026 includes sessions on running Istio in production, migrating from ingress-nginx, ambient mesh, AI inference serving, multicluster networking, encryption, and community leadership.

### Source excerpt

Get ready for a packed agenda of Istio activities at KubeCon + CloudNativeCon Europe 2026, including Cloud Native Theater Istio sessions featuring amazing speakers, hands-on experiences, and chances to meet maintainers and fellow community members in person. Istio highlights at KubeCon EU 2026 Join us at Cloud Native Theater on Tuesday, March 24, 2026 starting at 14:30 CET for 4 amazing Istio Day sessions: Tales From the Mesh: Horrors and Successes of Running Istio in Production -- A panel where real users of Istio share real world experiences, challenges, and wins with Istio service mesh. Zero-Downtime Migration from ingress-nginx to Istio in a Multi-Cluster Kubernetes Platform at Bloomberg -- Learn how Bloomberg migrated to Istio across multiple clusters without downtime. The Good, The Ugly, and The Bad: Leaving Sidecars Behind with Istio Ambient Mesh -- An honest look at migrating to ambient mesh architecture. Running State of the Art Inference with Istio and LLM-D -- Discover how Istio enables efficient AI inference serving. Join the Maintainer Track: Evolution or Revolution: Istio as the Network Platform for Cloud Native -- two maintainers explore how Istio's vision of a universal dataplane has guided the project's evolution, from powering global multicluster connectivity to enabling AI inference. Learn how you can contribute as an "Istio power user contributor" and share feedback on future improvements. Participate in the Cloud Native Novice Track: From First Contribution to Leadership: Lessons on Becoming a CNCF Leader -- a perfect session for newcomers interested in growing within the ecosystem. Learn about overcoming early challenges, maintaining momentum in large communities, and how authenticity, curiosity, and community support can accelerate your journey to leadership. Recommended Sessions at KubeCon Here are recommended sessions from the main conference with strong Istio relevance: From NLB Sprawl To Mesh Efficiency: How Skyscanner Handles 60M Requests Per M

## How to Secure Microservices with SPIFFE and Istio

DevFeed: [How to Secure Microservices with SPIFFE and Istio](<https://devfeed.tech/articles/how-to-secure-microservices-with-spiffe-and-istio-29691.md>)

Original publisher: [Read original article](<https://goteleport.com/blog/how-to-secure-microservices-spiffe-istio/>)

Author: info@goteleport.com (Jeff Ellin, Boris Kurktchiev)

Published: 2026-02-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [Teleport](<https://devfeed.tech/sources/teleport.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [SPIFFE](<https://devfeed.tech/topics/spiffe.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [certificates](<https://devfeed.tech/topics/certificates.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [backend](<https://devfeed.tech/tags/backend.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [firewalls](<https://devfeed.tech/tags/firewalls.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [policies](<https://devfeed.tech/tags/policies.md>), [secrets-management](<https://devfeed.tech/tags/secrets-management.md>), [security](<https://devfeed.tech/tags/security.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [spiffe](<https://devfeed.tech/tags/spiffe.md>), [zero-trust](<https://devfeed.tech/tags/zero-trust.md>)

### AI overview

This guide explains how to secure microservices with SPIFFE identities, Istio service-mesh mTLS, short-lived certificates, and Zero Trust authorization policies. It addresses the limits of network-based trust and long-lived certificates in dynamic Kubernetes environments.

### Source excerpt

Learn how to deploy a secure microservices application, configure default-deny authorization policies, and rebuild service connectivity with SPIFFE-based allow rules.

## Ambient multi-network multicluster support is now Beta

DevFeed: [Ambient multi-network multicluster support is now Beta](<https://devfeed.tech/articles/ambient-multi-network-multicluster-support-is-now-beta-48810.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/ambient-multinetwork-multicluster-beta/>)

Author: Gustavo Meira (Microsoft), Mikhail Krinkin (Microsoft)

Published: 2026-02-18T00:00:00Z

Content type: release

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Network](<https://devfeed.tech/topics/network.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ambient](<https://devfeed.tech/tags/ambient.md>), [beta](<https://devfeed.tech/tags/beta.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [distributed-system](<https://devfeed.tech/tags/distributed-system.md>), [gateways](<https://devfeed.tech/tags/gateways.md>), [istio](<https://devfeed.tech/tags/istio.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [multicluster](<https://devfeed.tech/tags/multicluster.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [release](<https://devfeed.tech/tags/release.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [services](<https://devfeed.tech/tags/services.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [waypoint](<https://devfeed.tech/tags/waypoint.md>), [xds](<https://devfeed.tech/tags/xds.md>), [ztunnel](<https://devfeed.tech/tags/ztunnel.md>)

### AI overview

Istio 1.29 introduces Beta support for ambient multi-network multicluster deployments, with improved telemetry, peer metadata discovery, connectivity, and reliability across distributed clusters and networks.

### Source excerpt

Our team of contributors has been busy throughout the transition to 2026. A lot of work was done to get the multi-network multicluster for ambient to production ready state. Improvements were made in areas from our internal tests, up to the most popular multi-network multicluster asks in ambient, with a big focus on telemetry. Gaps in Telemetry The benefits of a multicluster distributed system are not without their tradeoffs. Some complexity is inevitable with larger scale, making good telemetry even more important. The Istio team understands that point and we were aware of some gaps that needed to be covered. Thankfully, on release 1.29, telemetry is now more robust and complete when our ambient data plane operates over distributed clusters and networks. If you've deployed alpha multicluster capabilities before in multi-network scenarios, you might have noticed some source or destination labels would show as "unknown". For context, in a local cluster (or clusters sharing the same network), waypoint and ztunnel are aware of all existing endpoints, and they acquire that information through xDS. Confusing metrics instead often occur in multi-network deployments where, given all the information that needs to be replicated across separate networks, the xDS peer discovery is unpractical. Unfortunately, that results in missing peer information when requests traverse network boundaries to reach a different Istio cluster. Telemetry Enhancements Overcoming that problem, Istio 1.29 now ships with augmented discovery mechanisms in its data plane for exchanging peer metadata between endpoints and gateways sitting across different networks. The HBONE protocol is now enriched with baggage headers, allowing for waypoint and ztunnel to exchange peer information transparently through east-west gateways. Diagram showing peer metadata exchange across different networks In the diagram above, focusing on L7 metrics, we show how the peer metadata flows through baggage headers across diff

## Announcing Istio's 2026 Steering Committee Elections

DevFeed: [Announcing Istio's 2026 Steering Committee Elections](<https://devfeed.tech/articles/announcing-istio-s-2026-steering-committee-elections-48820.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/steering-election/>)

Author: Istio Steering Committee

Published: 2026-02-16T00:00:00Z

Content type: release

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [community](<https://devfeed.tech/tags/community.md>), [contributed](<https://devfeed.tech/tags/contributed.md>), [contribution](<https://devfeed.tech/tags/contribution.md>), [election](<https://devfeed.tech/tags/election.md>), [exception](<https://devfeed.tech/tags/exception.md>), [governance](<https://devfeed.tech/tags/governance.md>), [istio](<https://devfeed.tech/tags/istio.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [services](<https://devfeed.tech/tags/services.md>), [steering](<https://devfeed.tech/tags/steering.md>), [vote](<https://devfeed.tech/tags/vote.md>)

### AI overview

Istio announces its 2026 Steering Committee election. The article explains the allocation of nine Contribution Seats to four companies and invites eligible community members to nominate candidates for four Community Seats.

### Source excerpt

The Istio Steering Committee oversees the administrative aspects of the project, including governance, branding, marketing, and working with the CNCF. Every year, the leaders in the Istio project estimate the proportion of the hundreds of companies that have contributed to Istio in the past year, and uses that metric to proportionally allocate nine Contribution Seats on our Steering Committee. Then, four Community Seats are voted for by our project members, with candidates being from companies that did not receive Contribution Seats. We are pleased to share the result of this year's calculation, and to kick off our Community Seat election. Contribution seats The calculation for the 2026-2027 term reflects the deep investment of our vendors in the Istio open source project. We have four companies represented in our Contribution Seats: Company Seat allocation Solo.io 4 Microsoft 3 Red Hat 1 Tetrate 1 The full allocation can be seen in our formula spreadsheet. Community Seat election As in previous years, the Community Seat elections immediately follow the allocation of the Contribution Seats. It is therefore now time to collect our nominations for candidates, and ensure our voter list is correct. Candidates Eligibility for candidacy is defined in the Steering Committee charter as a project member who does not work for a Company that will hold a Contribution Seat during the upcoming term. We would now like to invite members from outside our Contribution Seat holders to stand for election. Nominations are due by March 6. Voters Eligibility to vote is defined in the charter as either: a project member who has had at least one Pull Request merged in the past 12 months, or someone who has submitted the voting exception form and has been accepted by the Steering Committee as having standing in the community through contribution of another kind. The draft list of voters has been published. If you're not on that list and you believe you have standing in the Istio community, p

## Capturing Network Packets in Kubernetes

DevFeed: [Capturing Network Packets in Kubernetes](<https://devfeed.tech/articles/capturing-network-packets-in-kubernetes-56802.md>)

Original publisher: [Read original article](<https://engineering.mercari.com/en/blog/entry/20251218-capturing-network-packets-in-kubernetes/>)

Author: Mshibuya

Published: 2025-12-18T11:00:28Z

Content type: tutorial

Language: en

Sources: [Mercari Engineering](<https://devfeed.tech/sources/mercari-engineering.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Network](<https://devfeed.tech/topics/network.md>), [site-reliability-engineering](<https://devfeed.tech/topics/site-reliability-engineering.md>), [istio](<https://devfeed.tech/topics/istio.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-clusters](<https://devfeed.tech/tags/kubernetes-clusters.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [mtls](<https://devfeed.tech/tags/mtls.md>), [network](<https://devfeed.tech/tags/network.md>), [network-packets](<https://devfeed.tech/tags/network-packets.md>), [sre](<https://devfeed.tech/tags/sre.md>)

### AI overview

A Mercari Platform Network and SRE team post explains why capturing network packets is difficult in Kubernetes environments and describes the need for stable, executable investigation procedures for complex network incidents. It discusses multi-tenant workload isolation, restricted node access, and encrypted service-mesh communication using Istio and mTLS.

### Source excerpt

This post is for Day 18 of Mercari Advent Calendar 2025, brought to you by @mshibuya from the Mercari Platform Network and SRE team. Today, I'm going to talk about capturing network packets in a Kubernetes environment. As mentioned above, I'm currently part of the Network team, where we build and operate the network-related components [...]

## Istio at KubeCon + CloudNativeCon North America 2025: A Week of Momentum, Community, and Milestones

DevFeed: [Istio at KubeCon + CloudNativeCon North America 2025: A Week of Momentum, Community, and Milestones](<https://devfeed.tech/articles/istio-at-kubecon-cloudnativecon-north-america-2025-a-week-of-momentum-community-and-milestones-48801.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2025/istio-at-kubecon-na/>)

Author: Faseela K, for the Istio Steering Committee

Published: 2025-11-25T00:00:00Z

Content type: news

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Security](<https://devfeed.tech/topics/security.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [API](<https://devfeed.tech/topics/api.md>), [migration](<https://devfeed.tech/topics/migration.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ambient-mesh](<https://devfeed.tech/tags/ambient-mesh.md>), [api](<https://devfeed.tech/tags/api.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [cloud-native-ecosystem](<https://devfeed.tech/tags/cloud-native-ecosystem.md>), [cloudnativecon](<https://devfeed.tech/tags/cloudnativecon.md>), [community](<https://devfeed.tech/tags/community.md>), [conference](<https://devfeed.tech/tags/conference.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [gateway-api](<https://devfeed.tech/tags/gateway-api.md>), [istio](<https://devfeed.tech/tags/istio.md>), [istio-day](<https://devfeed.tech/tags/istio-day.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [kubecon-na](<https://devfeed.tech/tags/kubecon-na.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [multicluster](<https://devfeed.tech/tags/multicluster.md>), [observability](<https://devfeed.tech/tags/observability.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [security](<https://devfeed.tech/tags/security.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

A report on Istio's presence at KubeCon + CloudNativeCon North America 2025, covering Istio Day sessions on service-mesh evolution, AI-ready infrastructure, multicluster Ambient Mesh, validation tooling, autoscaling, and stateful workloads.

### Source excerpt

Istio at KubeCon NA 2025 KubeCon + CloudNativeCon North America 2025 lit up Atlanta from November 10-13, bringing together one of the largest gatherings of open-source practitioners, platform engineers, and maintainers across the cloud native ecosystem. For the Istio community, the week was defined by packed rooms, long hallway conversations, and a genuine sense of shared progress across service mesh, Gateway API, security, and AI-driven platforms. Before the main conference began, the community kicked things off with Istio Day on November 10, a colocated event filled with deep technical sessions, migration stories, and future-looking discussions that set the tone for the rest of the week. Istio Day at KubeCon NA Istio Day brought together practitioners, contributors, and adopters for an afternoon of learning, sharing, and open conversations about where service mesh--and Istio--are headed next. IstioDay: North America Istio Day opened with Welcome + Opening Remarks from John Howard from Solo.io and Keith Mattix from Microsoft, setting the tone for an afternoon focused on real-world mesh evolution and the growing energy across the Istio community. The day quickly moved into applied AI with Is Your Service Mesh AI Ready?, where John Howard explored how traffic management, security, and observability shape production-grade AI workloads. IstioDay: Is Your Service Mesh AI Ready Momentum continued with Istio Ambient Goes Multicluster as Jackie Maertens and Steven Jin Xuan from Microsoft demonstrated how Ambient Mesh behaves across distributed clusters--highlighting identity, connectivity, and operational simplifications in multi-cluster deployments. A burst of energy came with the lightning talk Validating Your Istio Setups? The Tests Are Already Written, where Francisco Herrera Lira from Red Hat showed how built-in validation tooling can catch common configuration issues before they reach production. In Optimizing Istio Autoscaling: From Resource-Centric to Connection-Aware

## Istio at KubeCon North America 2025: Let's Connect in Atlanta!

DevFeed: [Istio at KubeCon North America 2025: Let's Connect in Atlanta!](<https://devfeed.tech/articles/istio-at-kubecon-north-america-2025-let-s-connect-in-atlanta-48803.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2025/kubecon-na/>)

Author: Francisco Herrera, for the Istio Community

Published: 2025-11-07T00:00:00Z

Content type: article

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [gateway](<https://devfeed.tech/topics/gateway.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [cloudnativecon](<https://devfeed.tech/tags/cloudnativecon.md>), [conference](<https://devfeed.tech/tags/conference.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [gateway-api](<https://devfeed.tech/tags/gateway-api.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [istio](<https://devfeed.tech/tags/istio.md>), [istio-day](<https://devfeed.tech/tags/istio-day.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [service](<https://devfeed.tech/tags/service.md>), [services](<https://devfeed.tech/tags/services.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

An announcement of Istio activities at KubeCon + CloudNativeCon North America 2025, including Istio Day sessions, workshops, contributor opportunities, and maintainer meetups. Topics include AI-ready service meshes, multicluster Ambient Mesh, testing, autoscaling, stateful workloads, Gateway APIs, and zero-downtime migrations.

### Source excerpt

Get ready for a packed agenda of Istio activities at KubeCon + CloudNativeCon North America 2025, including Istio Day sessions on AI-ready service meshes, multicluster Ambient Mesh, hands-on workshops, contributor opportunities, and chances to meet maintainers and fellow community members in person. Istio Day and Key Sessions Join us at Istio Day on Monday, November 10 2025 -- a full-day, community-focused event. Istio Day will feature sessions on AI readiness for service meshes, scaling Istio across multicluster environments with Ambient Mesh, validating and testing Istio setups, optimizing autoscaling, running stateful workloads like databases in Istio, and zero-downtime migrations to modern Gateway APIs. Attendees will also have hands-on workshops and opportunities to meet maintainers and contributors. Catch the TOC session: Istio Project Updates: AI Inference, Ambient Multicluster & Default Deny -- hear about the latest features, what the community has been working on, and a preview of the 2026 roadmap. Participate in Istio ContribFest: From Farm (Fork) To Table (Feature): Growing Your First (Free-range Organic) Istio PR -- a perfect session for newcomers and aspiring contributors to jump into the codebase and community. Recommended Sessions at KubeCon We gathered recommended sessions from the main conference with strong Istio relevance: Istio: Set Sailing With Istio Without Sidecars | Project Lightning Talk Lessons Applied Building a Next-generation AI Proxy Automated Rightsizing for Istio DaemonSet Workloads | Poster Session Gateway API: Table Stakes Know Before You Go! Speedrun Intro To Gateway API | Project Lightning Talk Return of the Mesh: Gateway API's Epic Quest for Unity 5 Key Lessons From 8 Years of Building Kgateway | Project Lightning Talk GAMMA in Action: How Careem Migrated To Istio Without Downtime Taming Rollout Risks in Distributed Web Apps: A Location-Aware Gradual Deployment Approach End-to-End Security With gRPC in Kubernetes On-Call the Easy Wa

## Istio Project Announces 2025 Technical Oversight Committee Election Results

DevFeed: [Istio Project Announces 2025 Technical Oversight Committee Election Results](<https://devfeed.tech/articles/istio-project-announces-2025-technical-oversight-committee-election-results-48808.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2025/toc-election-results/>)

Author: Craig Box, for the Istio Steering Committee

Published: 2025-08-19T00:00:00Z

Content type: news

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [mesh networking](<https://devfeed.tech/topics/mesh-networking.md>), [Network](<https://devfeed.tech/topics/network.md>), [proxy](<https://devfeed.tech/topics/proxy.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [community](<https://devfeed.tech/tags/community.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [election](<https://devfeed.tech/tags/election.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [governance](<https://devfeed.tech/tags/governance.md>), [istio](<https://devfeed.tech/tags/istio.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [mesh-networking](<https://devfeed.tech/tags/mesh-networking.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [networking](<https://devfeed.tech/tags/networking.md>), [project](<https://devfeed.tech/tags/project.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [services](<https://devfeed.tech/tags/services.md>), [toc](<https://devfeed.tech/tags/toc.md>)

### AI overview

The Istio Project announces the results of its 2025 Technical Oversight Committee election. Lin Sun and Louis Ryan were re-elected, and Rama Chavali won the third available seat.

### Source excerpt

Last year we announced that Istio would transform from an indefinitely-appointed Technical Oversight Committee to a regularly elected body, with members serving two-year terms. Each year, three of the six seats are elected. To bootstrap the process, we announced the 2025 election would cover the seats held by the three longest-serving members. One of those three seats became vacant, prompting a by-election. Long-time maintainer Costin Manolache won that election. We thank Costin for his continuing contributions and completing the remainder of the term, after which he chose not to stand again. Five candidates stood for the three available seats, and the Steering Committee has now concluded the election. Lin Sun and Louis Ryan were re-elected to their two seats. Both have been involved with Istio since before its public launch, and continue to serve as active leaders across the project. The third seat was won by Rama Chavali, a long-time contributor and maintainer of Istio through his work at Salesforce. In Rama's own words: I have worked with service mesh technologies for more than eight years, contributing to various projects that built the Managed Mesh platform for Salesforce. Istio and Envoy are the backbone of the Salesforce service mesh platform, powering critical workloads. The majority of Salesforce traffic flows through Istio and Envoy. I have been an active and impactful contributor to the Istio project since April 2019. My contributions span both the core control plane components of Istio and Envoy, the high-performance proxy that serves as Istio's data plane. Demonstrating a deep technical understanding and commitment to the project, I was recognized as a maintainer of Istio's control plane in January 2020. Building on this expertise in service mesh networking, I became a Networking Working Group lead in July 2020. Throughout my tenure, I have been instrumental in shaping the Istio project through the development and implementation of numerous significant

## Introducing multicluster support for ambient mode (alpha)

DevFeed: [Introducing multicluster support for ambient mode (alpha)](<https://devfeed.tech/articles/introducing-multicluster-support-for-ambient-mode-alpha-48797.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2025/ambient-multicluster/>)

Author: Jackie Maertens (Microsoft), Keith Mattix (Microsoft), Mikhail Krinkin (Microsoft), Steven Jin (Microsoft)

Published: 2025-08-04T00:00:00Z

Content type: release

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Security](<https://devfeed.tech/topics/security.md>), [gateway](<https://devfeed.tech/topics/gateway.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [data centers](<https://devfeed.tech/topics/data-centers.md>)

Tags: [ambient](<https://devfeed.tech/tags/ambient.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [multicluster](<https://devfeed.tech/tags/multicluster.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [scale](<https://devfeed.tech/tags/scale.md>), [scale-across](<https://devfeed.tech/tags/scale-across.md>), [security](<https://devfeed.tech/tags/security.md>), [services](<https://devfeed.tech/tags/services.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

Istio 1.27 introduces alpha support for multicluster ambient mode. The release extends ambient's lightweight, modular architecture to provide secure connectivity, service discovery, and load balancing across Kubernetes clusters, while preserving existing service DNS names.

### Source excerpt

Multicluster has been one of the most requested features of ambient --- and as of Istio 1.27, it is available in alpha status! We sought to capture the benefits and avoid the complications of multicluster architectures while using the same modular design that ambient users love. This release brings the core functionality of a multicluster mesh and lays the groundwork for a richer feature set in upcoming releases. The Power & Complexity of Multicluster Multicluster architectures increase outage resilience, shrink your blast radius, and scale across data centers. That said, integrating multiple clusters poses connectivity, security, and operational challenges. In a single Kubernetes cluster, every pod can directly connect to another pod via a unique pod IP or service VIP. These guarantees break down in multicluster architectures; IP address spaces of different clusters might overlap, and even without overlap, the underlying infrastructure would need configuration to route cross-cluster traffic. Cross-cluster connectivity also presents security challenges. Pod-to-pod traffic will leave cluster boundaries and pods will accept connections from outside their cluster. Without identity verification at the edge of the cluster and strong encryption, an outside attacker could exploit a vulnerable pod or intercept unencrypted traffic. A multicluster solution must securely connect clusters and do so through simple, declarative APIs that keep pace with dynamic environments where clusters are frequently added and removed. Key Components Ambient multicluster extends ambient with new components and minimal APIs to securely connect clusters using ambient's lightweight, modular architecture. It builds on the namespace sameness model so services keep their existing DNS names across clusters, allowing you to control cross-cluster communication without changing application code. East-West Gateways Each cluster has an east-west gateway with a globally routable IP acting as an entry point f

## Bringing AI-Aware Traffic Management to Istio: Gateway API Inference Extension Support

DevFeed: [Bringing AI-Aware Traffic Management to Istio: Gateway API Inference Extension Support](<https://devfeed.tech/articles/bringing-ai-aware-traffic-management-to-istio-gateway-api-inference-extension-support-48799.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2025/inference-extension-support/>)

Author: Lior Lieberman (Google), Keith Mattix (Microsoft), Aslak Knutsen (Red Hat)

Published: 2025-07-28T00:00:00Z

Content type: release

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [GPU](<https://devfeed.tech/topics/gpu.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [gateway-api-inference-extension](<https://devfeed.tech/tags/gateway-api-inference-extension.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inference](<https://devfeed.tech/tags/inference.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [large-language-model](<https://devfeed.tech/tags/large-language-model.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [rag](<https://devfeed.tech/tags/rag.md>), [services](<https://devfeed.tech/tags/services.md>), [traffic-management](<https://devfeed.tech/tags/traffic-management.md>)

### AI overview

Istio announces support for the Gateway API Inference Extension, adding model-aware and LoRA-aware traffic routing for AI inference workloads on Kubernetes. The article explains why LLM requests require specialized routing because of their longer duration, larger payloads, streaming and timeout needs, and intensive GPU resource consumption.

### Source excerpt

The world of AI inference on Kubernetes presents unique challenges that traditional traffic-routing architectures weren't designed to handle. While Istio has long excelled at managing microservice traffic with sophisticated load balancing, security, and observability features, the demands of Large Language Model (LLM) workloads require specialized functionality. That's why we're excited to announce Istio's support for the Gateway API Inference Extension, bringing intelligent, model-aware and LoRA-aware routing to Istio. Why AI Workloads Need Special Treatment Traditional web services typically handle quick, stateless requests measured in milliseconds. AI inference workloads operate in a completely different paradigm that challenges conventional load balancing approaches in several fundamental ways. The Scale and Duration Challenge Unlike typical API responses that complete in milliseconds, AI inference requests often take significantly longer to process - sometimes several seconds or even minutes. This dramatic difference in processing time means that routing decisions have far more impact than in traditional web services. A single poorly-routed request can tie up expensive GPU resources for extended periods, creating cascading effects across the entire system. The payload characteristics are equally challenging. AI inference requests frequently involve substantially larger payloads, especially when dealing with Retrieval-Augmented Generation (RAG) systems, multi-turn conversations with extensive context, or multi-modal inputs including images, audio, or video. These large payloads require different buffering, streaming, and timeout strategies than traditional HTTP APIs. Resource Consumption Patterns Perhaps most critically, a single inference request can consume an entire GPU's resources during processing. This is fundamentally different from traditional request serving where multiple requests can be processed concurrently on the same compute resources. When a GPU

[Next page](<https://devfeed.tech/topics/istio.md?cursor=WyIyMDI1LTA3LTI4VDAwOjAwOjAwKzAwOjAwIiwgImE4YjM1OTdkLThhNTAtNDQzMy1iMzgyLTIzNmFhMzVkNmQ0YyJd>)