# service-mesh

A service mesh is an infrastructure layer in an application that facilitates communication between services and provides capabilities such as traffic management, resiliency, policy, security, identity, and observability.

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

## Top 13 Microservices Interview Questions Answered

DevFeed: [Top 13 Microservices Interview Questions Answered](<https://devfeed.tech/articles/top-13-microservices-interview-questions-answered-146768.md>)

Original publisher: [Read original article](<https://newsletter.systemdesign.one/p/microservices-interview-questions>)

Author: Neo Kim

Published: 2026-11-20T12:02:22Z

Content type: article

Language: en

Sources: [System Design Newsletter](<https://devfeed.tech/sources/system-design-newsletter.md>)

Topics: [Microservices](<https://devfeed.tech/topics/microservices.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [observability](<https://devfeed.tech/topics/observability.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [modular-monolith](<https://devfeed.tech/topics/modular-monolith.md>), [monolithic-architecture](<https://devfeed.tech/topics/monolithic-architecture.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [interview](<https://devfeed.tech/tags/interview.md>), [interview-questions](<https://devfeed.tech/tags/interview-questions.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [questions](<https://devfeed.tech/tags/questions.md>), [top](<https://devfeed.tech/tags/top.md>)

### AI overview

The article presents 13 microservices interview questions and stresses weighing operational costs against benefits. Microservices enable independent releases and scaling, but introduce network failures, distributed data, and tooling needs; for a small team or new product, it recommends starting with a modular monolith and extracting services when concrete pressures emerge. It explains boundaries based on business capabilities and bounded contexts, service-owned data with APIs or event-fed copies, and sagas with compensating actions for workflows spanning services. Other guidance distinguishes API gateways from load balancers and service meshes, client-side from server-side discovery, and SOA from microservices. It also covers circuit breakers, distributed tracing, shared rate-limit counters across gateway instances, and REST conventions such as idempotency keys for retried order requests.

### Source excerpt

#205: Ace Software Engineering Job Interviews

## How to Secure an Internal-Only Microservice in Kubernetes

DevFeed: [How to Secure an Internal-Only Microservice in Kubernetes](<https://devfeed.tech/articles/how-to-secure-an-internal-only-microservice-in-kubernetes-136403.md>)

Original publisher: [Read original article](<https://kodekloud.com/blog/secure-internal-microservices/>)

Author: Nimesha Jinarajadasa

Published: 2026-11-16T09:10:18Z

Content type: tutorial

Language: en

Sources: [KodeKloud](<https://devfeed.tech/sources/kubernetes-kodekloud-blog-devops-cloud-kubernetes-ai-tutorials-more.md>)

Topics: [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [linkerd](<https://devfeed.tech/topics/linkerd.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [identity](<https://devfeed.tech/tags/identity.md>), [ip](<https://devfeed.tech/tags/ip.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linkerd](<https://devfeed.tech/tags/linkerd.md>), [loadbalancer](<https://devfeed.tech/tags/loadbalancer.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [mtls](<https://devfeed.tech/tags/mtls.md>), [mutual-tls](<https://devfeed.tech/tags/mutual-tls.md>), [network](<https://devfeed.tech/tags/network.md>), [policies](<https://devfeed.tech/tags/policies.md>), [private](<https://devfeed.tech/tags/private.md>), [security](<https://devfeed.tech/tags/security.md>), [service](<https://devfeed.tech/tags/service.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

A ClusterIP service keeps the payments service off the public internet, but does not restrict traffic from other pods: Kubernetes' flat cluster network could let a compromised marketing pod reach it. The text recommends layering an allowlist network policy for order-service pods, then mutual TLS to verify service identities with short-lived certificates. It notes that network policies identify traffic by source address, which can change as pods restart or move. Istio or Linkerd can manage certificates and encrypt service traffic through sidecar proxies without changing application logic. A further service-mesh authorization policy can restrict which services each caller may invoke, such as allowing order to call payments but not refunds.

### Source excerpt

Secure an internal-only microservice in Kubernetes with a private ClusterIP, network policies, mutual TLS in a service mesh and authz policies.

## 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

## Red Hat OpenShift 5: What partners need to know

DevFeed: [Red Hat OpenShift 5: What partners need to know](<https://devfeed.tech/articles/red-hat-openshift-5-what-partners-need-to-know-126520.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/red-hat-openshift-5-what-partners-need-know>)

Author: Jackie Rose

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

Content type: article

Language: en

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

Topics: [redhat](<https://devfeed.tech/topics/redhat.md>), [Cloud & Application Security](<https://devfeed.tech/topics/cloud-application-security.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Cloud Native Operations](<https://devfeed.tech/topics/cloud-native-operations.md>)

Tags: [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [application-platform](<https://devfeed.tech/tags/application-platform.md>), [automation](<https://devfeed.tech/tags/automation.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cluster-security](<https://devfeed.tech/tags/cluster-security.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [pairing](<https://devfeed.tech/tags/pairing.md>), [partners](<https://devfeed.tech/tags/partners.md>), [platform](<https://devfeed.tech/tags/platform.md>), [product](<https://devfeed.tech/tags/product.md>), [product-release](<https://devfeed.tech/tags/product-release.md>), [red-hat-openshift-5](<https://devfeed.tech/tags/red-hat-openshift-5.md>), [relationships](<https://devfeed.tech/tags/relationships.md>), [release](<https://devfeed.tech/tags/release.md>), [resellers](<https://devfeed.tech/tags/resellers.md>), [security](<https://devfeed.tech/tags/security.md>), [support](<https://devfeed.tech/tags/support.md>)

### AI overview

Red Hat OpenShift 5 is positioned as a way for partners to expand customer workloads and retain accounts while supporting virtual machines, containers, and AI applications across on-premises, cloud, and edge environments. The text highlights natural-language tooling and agentic operations, including OpenShift Lightspeed, for faster troubleshooting and onboarding; security features including post-quantum cryptography, hardware-level isolation, and stronger identity controls for sensitive workloads; and a clearer release cadence with up to five years of support on Extended Life Cycle releases. It says customers can update from OpenShift 4 in place, much like a minor release, and that many receive OpenShift 5 through existing subscriptions. Partners may pair the platform with security, GitOps, pipelines, service mesh, and observability offerings as customer environments grow.

### Source excerpt

Red Hat OpenShift 5 is the next evolution of the cloud-native application platform you and your customers already trust.For distributors and resellers, Red Hat OpenShift 5 is more than a product release--it's a growth opportunity: longer customer relationships, clearer lifecycle conversations, and improved support for sovereign, regulated, and AI workloads. It also creates more natural ways to expand the deal beyond the core platform--for example, pairing Red Hat OpenShift with security (such as Red Hat Advanced Cluster Security for Kubernetes), automation and delivery tooling (Red Hat Ope

## Service mesh: what it buys and the latency it charges

DevFeed: [Service mesh: what it buys and the latency it charges](<https://devfeed.tech/articles/service-mesh-what-it-buys-and-the-latency-it-charges-124066.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/73-service-mesh-what-it-buys-and-charges/>)

Author: hello@ankit-rana.com

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

Content type: opinion

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [traffic splitting](<https://devfeed.tech/topics/traffic-splitting.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [envoy](<https://devfeed.tech/tags/envoy.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [latency](<https://devfeed.tech/tags/latency.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>)

### AI overview

A sidecar service mesh adds two proxy crossings to each service call; the article estimates 0.5-2 ms of added latency per call, with worse tail latency, plus roughly 50-150 MB of memory and some CPU per pod. These costs compound along deep call chains and across pod counts. The comparison is not mesh versus no capabilities: without a mesh, mTLS, retries, circuit breaking, load balancing and telemetry must be implemented and upgraded in service libraries, potentially across languages. A mesh is most compelling for many services across several languages, mandatory estate-wide encryption, traffic splitting, or telemetry for components you do not control. It is less attractive for a small, single-language system, latency-critical deep paths, or teams without platform ownership. For an existing mesh, measure injected versus bypassed latency on the same service, configure retries in one layer, place proxy metrics beside application metrics, and consider ambient or sidecarless modes when per-pod memory is the main constraint, accepting less per-pod isolation.

### Source excerpt

A sidecar proxy adds two extra network hops per call, typically half a millisecond to two milliseconds of added latency plus memory and CPU per pod. The comparison people make is against having nothing, which is wrong, because the mTLS, retries, circuit breaking and telemetry it provides were previously implemented as libraries that had their own cost and had to be upgraded across every service. A mesh is worth it when you have enough services in enough languages that library sprawl is the larger problem, and it is overhead when you do not.

## How We Load-Test 700+ Independently-Owned Services Without Touching Production

DevFeed: [How We Load-Test 700+ Independently-Owned Services Without Touching Production](<https://devfeed.tech/articles/how-we-load-test-700-independently-owned-services-without-touching-production-113423.md>)

Original publisher: [Read original article](<https://medium.com/myntra-engineering/how-we-load-test-700-independently-owned-services-without-touching-production-5a48f6bf89ce?source=rss----7484818e9f88---4>)

Author: Vasuman Mishra

Published: 2026-11-02T14:01:26Z

Content type: article

Language: en

Sources: [Myntra](<https://devfeed.tech/sources/myntra.md>)

Topics: [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [linkerd](<https://devfeed.tech/topics/linkerd.md>), [internal developer platform](<https://devfeed.tech/topics/internal-developer-platform.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [Automation](<https://devfeed.tech/topics/automation.md>)

Tags: [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [devops](<https://devfeed.tech/tags/devops.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linkerd](<https://devfeed.tech/tags/linkerd.md>), [load](<https://devfeed.tech/tags/load.md>), [load-testing](<https://devfeed.tech/tags/load-testing.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [production](<https://devfeed.tech/tags/production.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scale](<https://devfeed.tech/tags/scale.md>), [services](<https://devfeed.tech/tags/services.md>), [teams](<https://devfeed.tech/tags/teams.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Myntra load-tests services in the production cluster without sending test traffic through production deployments by using a patched Linkerd proxy that adds an NFR header to outbound requests. At each mesh hop, requests with that header go to an available NFR deployment; when none exists, traffic falls back to the production dependency. This avoids a second cluster and application changes across 100+ services, though load-test scripts need a one-time header update. A self-serve UI lets service owners assemble and disassemble NFR deployments, reuses existing production approval groups for access, and marks failed setups as PARTIAL. For Birthday Bash 2026, Myntra reports testing 70 services in parallel and completing certification in three days. The excerpt says databases, caches, and Kafka flows still need separate routing approaches, and the header patch remains a Linkerd fork.

### Source excerpt

The problem with testing at scale, the routing trick that solved it, and the UI that made it something any team could use on their own At Myntra, reliability on a sale day is the priority. When marquee events like Big Fashion Festival (BFF), End of Reason Sale (EORS), or Myntra Birthday Bash land, hundreds of thousands of customers show up within the same few hours, and every one of those sessions has to hold up exactly as well as any other normal day. A slow page or a failed checkout during a sale defines the entire experience for that customer, translating directly into brand image loss and massive opportunity cost. So a good part of our time in the weeks before a sale focuses on two critical tracks: accurate sale traffic prediction, and executing rigorous scale testing against that predicted traffic. Getting a real answer means load-testing hundreds of services under production-like conditions. Say that out loud and the problem is obvious: you can't safely fire a full-scale load test at production, and you also can't afford to build and run a second production just to test against. This is how we built our way around that, without a second production and without asking a hundred-plus teams to change how they work. And how we then turned it from something only the platform team could operate into something any engineering manager could run on their own. The problem: three ways to fail at this Myntra runs 500+ microservices, each owned by its own team. We needed to leverage our existing underlying infrastructure rather than reinventing it, driven by two core principles: Identical underlying infrastructure: Using the exact same cluster environment eliminates unexpected behavioral differences and surprise elements between scale testing and live production. Zero application-level changes: Services must continue calling the same URLs and dependencies without teams rewriting networking or business logic. Zero production blast radius: Production traffic cannot take a hit

## The Linkerd Story: The people Behind The Service Mesh -- A new documentary premieres at KubeCon + CloudNativeCon North America 2026

DevFeed: [The Linkerd Story: The people Behind The Service Mesh -- A new documentary premieres at KubeCon + CloudNativeCon North America 2026](<https://devfeed.tech/articles/the-linkerd-story-the-people-behind-the-service-mesh-a-new-documentary-premieres-at-kubecon-cloudnativecon-north-america-2026-112427.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/11/02/the-linkerd-story-the-people-behind-the-service-mesh-a-new-documentary-premieres-at-kubecon-cloudnativecon-north-america-2026/>)

Author: epower

Published: 2026-11-02T12:00:00Z

Content type: release

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

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

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [blog](<https://devfeed.tech/tags/blog.md>), [documentary](<https://devfeed.tech/tags/documentary.md>), [linkerd](<https://devfeed.tech/tags/linkerd.md>), [people](<https://devfeed.tech/tags/people.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>)

### AI overview

The documentary traces Linkerd from engineering challenges at Twitter and experience with Finagle to a Kubernetes-focused service mesh, including its adoption of Rust for lightweight sidecar proxies. It highlights technical decisions alongside the contributors, maintainers, ambassadors, and users who sustained the project, its path to CNCF graduation, and the role of open governance and collaboration. A H-E-B curbside services example illustrates its use in practice. The article announces a premiere at KubeCon + CloudNativeCon North America 2026 in Salt Lake City on November 9; it frames Linkerd's decade-long history around the people and community behind open source.

### Source excerpt

Join CNCF and Buoyant on November 9 in Salt Lake City for the premiere of a new documentary celebrating a decade of Linkerd, the evolution of service mesh technology, and the people who helped make it...

## From Infrastructure to Agents: A Hands-on Guide to Secure Private AI with Broadcom - Part 4

DevFeed: [From Infrastructure to Agents: A Hands-on Guide to Secure Private AI with Broadcom - Part 4](<https://devfeed.tech/articles/from-infrastructure-to-agents-a-hands-on-guide-to-secure-private-ai-with-broadcom-part-4-105700.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/28/from-infrastructure-to-agents-a-hands-on-guide-to-secure-private-ai-with-broadcom-part-4/>)

Author: niran evenchen and william arroyo

Published: 2026-10-28T11:38:02Z

Content type: tutorial

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [ai security](<https://devfeed.tech/topics/ai-security.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-coding](<https://devfeed.tech/tags/agentic-coding.md>), [agentic-governance](<https://devfeed.tech/tags/agentic-governance.md>), [agentic-loop](<https://devfeed.tech/tags/agentic-loop.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [context](<https://devfeed.tech/tags/context.md>), [home-page](<https://devfeed.tech/tags/home-page.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [instructions](<https://devfeed.tech/tags/instructions.md>), [memory](<https://devfeed.tech/tags/memory.md>), [model](<https://devfeed.tech/tags/model.md>), [platform](<https://devfeed.tech/tags/platform.md>), [private-ai](<https://devfeed.tech/tags/private-ai.md>), [skills](<https://devfeed.tech/tags/skills.md>), [tools](<https://devfeed.tech/tags/tools.md>), [vmware](<https://devfeed.tech/tags/vmware.md>)

### AI overview

The lab shows how Tanzu Platform and AgentMinder govern an agent's connections and actions: Tanzu service bindings provide approved model and MCP connection details, while AgentMinder grants authorize specific tool intents on the VCF path. Kubernetes calls in the demo go directly to Kubernetes MCP and rely on its credentials and permissions; VCF calls pass through the AgentMinder sidecar and gateway, where VM and network intents are granted separately. The walkthrough also uses Tanzu AI Services webhooks with a Presidio-based scrubber to replace detected PII on the model path. Runtime containment, deny-by-default network rules, backend restrictions, and audit records complement these controls. The text cautions that tool visibility does not imply permission, cached tokens may retain old scopes until refreshed, and gateway enforcement alone does not prove bypass routes are closed. The demonstrated VM grant included mutation tools; a narrower read-only intent would need separate configuration.

### Source excerpt

Part 4 of 4: Governing the Agentic Loop - Bringing Platform as a Service and Governed Agentic Loop with Tanzu and AgentMinder An AI agent needs more than a model. It needs instructions and skills, memory to retain context, and tools that let it interact with the systems around it. Every connection makes the agent ... Continued The post From Infrastructure to Agents: A Hands-on Guide to Secure Private AI with Broadcom - Part 4 appeared first on VMware Blogs.

## Service Discovery: Types, Benefits & How It Works

DevFeed: [Service Discovery: Types, Benefits & How It Works](<https://devfeed.tech/articles/service-discovery-types-benefits-how-it-works-105581.md>)

Original publisher: [Read original article](<https://talent500.com/blog/service-discovery/>)

Author: Ekakshar

Published: 2026-10-28T09:42:53Z

Content type: article

Language: en

Sources: [Talent500](<https://devfeed.tech/sources/backend-archives-talent500-blog.md>)

Topics: [CoreDNS Kubernetes](<https://devfeed.tech/topics/coredns-kubernetes.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [apache-zookeeper](<https://devfeed.tech/tags/apache-zookeeper.md>), [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [backend](<https://devfeed.tech/tags/backend.md>), [balancing](<https://devfeed.tech/tags/balancing.md>), [cache](<https://devfeed.tech/tags/cache.md>), [client-side-service-discovery](<https://devfeed.tech/tags/client-side-service-discovery.md>), [cloud-native-applications](<https://devfeed.tech/tags/cloud-native-applications.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [communication](<https://devfeed.tech/tags/communication.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [server-side-service-discovery](<https://devfeed.tech/tags/server-side-service-discovery.md>), [service-discovery](<https://devfeed.tech/tags/service-discovery.md>), [service-discovery-in-microservices](<https://devfeed.tech/tags/service-discovery-in-microservices.md>), [service-discovery-tools](<https://devfeed.tech/tags/service-discovery-tools.md>), [service-discovery-vs-load-balancing](<https://devfeed.tech/tags/service-discovery-vs-load-balancing.md>), [service-registry](<https://devfeed.tech/tags/service-registry.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

Service discovery lets applications find current service instances as infrastructure changes, replacing hardcoded addresses with registration, lookup, health monitoring, and routing. In client-side discovery, each application retrieves endpoints and selects an instance, gaining routing control but requiring discovery logic and handling of stale data. In server-side discovery, a proxy, gateway, or load balancer selects the destination, simplifying clients while adding routing infrastructure and potentially another network hop. Kubernetes Services and DNS provide stable in-cluster names; Consul supports discovery across varied environments; Eureka is commonly used with Spring ecosystems and client-side discovery; Istio adds mesh traffic management, security, and observability; ZooKeeper is a general coordination system that may need extra discovery logic. Discovery can supply destinations for load balancing but does not itself ensure resilience: health checks, timeouts, careful retries, and failure handling matter, and discovery cannot create capacity when all instances fail.

### Source excerpt

Discover how Service Discovery enables applications in distributed systems and microservices architectures to locate and communicate with services dynamically. Explore its types, working mechanisms, tools, benefits, and implementation approaches for building scalable, resilient, and reliable applications. The post Service Discovery: Types, Benefits & How It Works appeared first on Talent500 blog.

## Governing Enterprise AI Traffic at Scale: Design and Operation of a Policy-Driven, Multi-Vendor LLM Gateway on Envoy

DevFeed: [Governing Enterprise AI Traffic at Scale: Design and Operation of a Policy-Driven, Multi-Vendor LLM Gateway on Envoy](<https://devfeed.tech/articles/governing-enterprise-ai-traffic-at-scale-design-and-operation-of-a-policy-driven-multi-vendor-llm-gateway-on-envoy-101634.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.35509>)

Author: Mithun Sasidharan, Srinivasan Manoharan, Rupesh Thakur, Abhinav TK, Ashwin Hegde, Anand Gautam

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [litellm](<https://devfeed.tech/topics/litellm.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Open Policy Agent](<https://devfeed.tech/topics/open-policy-agent.md>), [policy-as-code](<https://devfeed.tech/topics/policy-as-code.md>), [data loss prevention](<https://devfeed.tech/topics/data-loss-prevention.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authoring](<https://devfeed.tech/tags/authoring.md>), [availability](<https://devfeed.tech/tags/availability.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [budget](<https://devfeed.tech/tags/budget.md>), [cache](<https://devfeed.tech/tags/cache.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [design](<https://devfeed.tech/tags/design.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-gateway](<https://devfeed.tech/tags/llm-gateway.md>), [policy](<https://devfeed.tech/tags/policy.md>), [scale](<https://devfeed.tech/tags/scale.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

The Cosmos LLM Gateway at PayPal separates latency-sensitive work: authentication, credential brokering, policy and budget checks run in an out-of-process service, while a Rust WebAssembly filter inside Envoy handles format translation, token metering and prompt-cache shaping. This lets streamed response chunks avoid out-of-process waits by default. Open Policy Agent evaluates declarative policies managed through role-scoped authoring, approvals, pilots, shadow rollouts, notifications and versioned bundles. Optional data-loss prevention can block, redact or pseudonymize detected sensitive content before provider access; spend scopes apply budgets to usage already recorded in the budget window. As of September 2026, the gateway serves over 12,000 developers, handles about 200 billion tokens daily across 100-plus models, and reports 99.999% business availability. A core-path benchmark against a synthetic upstream measured 4 ms median and 11 ms p99 overhead at over 2,200 requests per second on two 4-vCPU instances.

### Source excerpt

arXiv:2610.35509v1 Announce Type: new Abstract: Large organizations consume large language models (LLMs) from several vendors at once, each with its own API dialect, credential model, streaming protocol and pricing. Integrated directly, this heterogeneity yields credential sprawl, format lock-in, unbounded spend and inconsistent governance. We present the design and production operation of the Cosmos LLM Gateway, the governed entry point for enterprise LLM traffic at PayPal. Built on Envoy, it splits work by latency profile: I/O-bound control decisions (authentication, credential brokering, policy and budget evaluation) run in an out-of-process external-processing service, while wire-format translation, token metering and prompt-cache shaping run in-proxy as a Rust WebAssembly filter, so that, by default, streamed response body chunks never wait on an out-of-process call. Models, providers and prices are largely validated data rather than code. Governance is declarative policy evaluated by Open Policy Agent and managed through a control plane with role-scoped authoring, approvals, pilots, shadow-mode rollout, usage notifications and versioned policy bundles. For use cases that require it, a data-loss-prevention layer can block, redact or pseudonymize detected sensitive content before it reaches a provider. Spend scopes are views over per-model usage counters, so a new budget applies to spend already recorded in its window without migration. As of September 2026, the gateway serves more than 12,000 developers and hundreds of business use cases, handling roughly 200 billion tokens per day across more than 100 models at 99.999% availability to business. In a benchmark of the core request path against a synthetic upstream, it adds a median of 4 ms and a p99 of 11 ms of overhead at more than 2,200 requests per second on two 4-vCPU instances. We report the architecture, policy model, evaluation and lessons learned.

## 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

## Agent Security & Identity (Part 2): Who Are You, Who's Your Agent, And What Should They Be Allowed?

DevFeed: [Agent Security & Identity (Part 2): Who Are You, Who's Your Agent, And What Should They Be Allowed?](<https://devfeed.tech/articles/agent-security-identity-part-2-who-are-you-who-s-your-agent-and-what-should-they-be-allowed-97763.md>)

Original publisher: [Read original article](<https://hackernoon.com/agent-security-and-identity-part-2-who-are-you-whos-your-agent-and-what-should-they-be-allowed?source=rss>)

Author: Alejandro Saucedo

Published: 2026-10-23T11:00:02Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Security](<https://devfeed.tech/topics/security.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2-2](<https://devfeed.tech/tags/2-2.md>), [3](<https://devfeed.tech/tags/3.md>), [3-questions](<https://devfeed.tech/tags/3-questions.md>), [about](<https://devfeed.tech/tags/about.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [account](<https://devfeed.tech/tags/account.md>), [actor](<https://devfeed.tech/tags/actor.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-auth](<https://devfeed.tech/tags/agent-auth.md>), [agent-delegation](<https://devfeed.tech/tags/agent-delegation.md>), [agent-gateway](<https://devfeed.tech/tags/agent-gateway.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agent-orchestration](<https://devfeed.tech/tags/agent-orchestration.md>), [agent-security](<https://devfeed.tech/tags/agent-security.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-security](<https://devfeed.tech/tags/agentic-security.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [ai-agent-identity](<https://devfeed.tech/tags/ai-agent-identity.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-ethics](<https://devfeed.tech/tags/ai-ethics.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [identity](<https://devfeed.tech/tags/identity.md>), [security](<https://devfeed.tech/tags/security.md>), [series](<https://devfeed.tech/tags/series.md>)

### AI overview

The walkthrough demonstrates KAOS enforcing identity and authorization at a gateway on a local KIND cluster. Alice, in the `researchers` group, can invoke `researcher`; Bob, in `support`, is denied. The agent's declared tool and model dependencies supply its permissions, while autonomous `autobot` acts under its own identity and a user-facing agent without a user is denied. Authorization fails closed if the service is unavailable, a choice the article says carries an availability cost and motivates running it with multiple replicas. For GitHub, the Agent Identity Broker stores consented user credentials and exchanges them on a specific outbound route, so the agent does not handle the long-lived token; users can revoke consent independently. The demo uses mock GitHub, so it demonstrates the delegation path, not GitHub's behavior.

### Source excerpt

Part 2 of a 2-part series on agent identity and security

## 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

## Uber Automates Dependency Analysis Across Its Service Mesh

DevFeed: [Uber Automates Dependency Analysis Across Its Service Mesh](<https://devfeed.tech/articles/uber-automates-dependency-analysis-across-its-service-mesh-88464.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/uber-automated-dependency/>)

Author: Leela Kumili

Published: 2026-10-16T14:39:00Z

Content type: news

Language: en

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

Topics: [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>)

Tags: [analysis](<https://devfeed.tech/tags/analysis.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [failure](<https://devfeed.tech/tags/failure.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [middleware-management](<https://devfeed.tech/tags/middleware-management.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [rpc](<https://devfeed.tech/tags/rpc.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [service-reliability](<https://devfeed.tech/tags/service-reliability.md>), [uber-automated-dependency](<https://devfeed.tech/tags/uber-automated-dependency.md>)

### AI overview

Uber describes a middleware-based system that correlates caller and downstream service failures to classify dependencies as fail-close, fail-open, or unknown. It uses production metrics to map failure propagation across its service mesh, aiming to analyze rare failures faster than sampled tracing allows.

### Source excerpt

Uber has developed an automated dependency analysis system that uses RPC middleware and production metrics to correlate caller and downstream failures. The approach classifies dependencies as fail-close, fail-open, or unknown and addresses limitations of sampled distributed tracing for rare failures across Uber's large service mesh. By Leela Kumili

## Master Open Policy Agent (OPA)

DevFeed: [Master Open Policy Agent (OPA)](<https://devfeed.tech/articles/master-open-policy-agent-opa-64350.md>)

Original publisher: [Read original article](<https://blog.devops.dev/master-open-policy-agent-opa-653cdc6b5850?source=rss----33f8b2d9a328---4>)

Author: Suranga Jayalath

Published: 2026-10-03T13:31:21Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Open Policy Agent](<https://devfeed.tech/topics/open-policy-agent.md>), [rego](<https://devfeed.tech/topics/rego.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [beginner](<https://devfeed.tech/tags/beginner.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud-native-computing-foundation](<https://devfeed.tech/tags/cloud-native-computing-foundation.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [decision-making](<https://devfeed.tech/tags/decision-making.md>), [devops](<https://devfeed.tech/tags/devops.md>), [engine](<https://devfeed.tech/tags/engine.md>), [json](<https://devfeed.tech/tags/json.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [opa](<https://devfeed.tech/tags/opa.md>), [opas](<https://devfeed.tech/tags/opas.md>), [open-policy-agent](<https://devfeed.tech/tags/open-policy-agent.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [policy](<https://devfeed.tech/tags/policy.md>), [policy-enforcement](<https://devfeed.tech/tags/policy-enforcement.md>), [policy-management](<https://devfeed.tech/tags/policy-management.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

Open Policy Agent (OPA) separates policy decisions from application logic: a service sends OPA a JSON input, OPA evaluates it against a policy written in Rego, and returns a JSON decision. The excerpt highlights use for Kubernetes admission control through Gatekeeper, API and microservice authorization, and Terraform or CloudFormation checks in CI/CD. It illustrates a Rego rule that allows an Ingress only when TLS is present, and recommends keeping policy tests alongside policy files. The excerpt says policies can be updated without rebuilding application binaries, while its Gatekeeper flow rejects denied Kubernetes requests with an error. The supplied text does not include details of the promised advantages-versus-disadvantages comparison.

### Source excerpt

If you've ever had to hardcode authorization logic inside a microservice or manually check whether your Kubernetes deployment YAMLs meet security standards you know how messy policy management can get. Every service ends up implementing its own authorization logic in a slightly different way. When compliance requirements change, you have to modify, test, and redeploy every single application. Enter Open Policy Agent (OPA). In this beginner-friendly guide, we'll demystify what OPA is, why it has become the cloud-native standard for policy enforcement, and how to write your first policy from scratch. What is Open Policy Agent (OPA)? Open Policy Agent (pronounced "oh-pa") is an open-source, general-purpose policy engine hosted by the CNCF (Cloud Native Computing Foundation). Instead of hardcoding security rules inside your backend APIs, CI/CD pipelines, or Kubernetes clusters, OPA decouples policy decision-making from application logic. How It Works Your service receives a request or trigger. Your service sends a JSON document (the input) to OPA asking: "Is this allowed?" OPA evaluates the input against a pre-written policy file. OPA returns a JSON response with the decision (e.g., true/false, a list of errors, or an allowed role). Because OPA accepts any JSON input and returns any JSON output, it works across your entire tech stack from microservice APIs to Terraform configurations and Kubernetes manifests. Why Do You Need OPA? Before OPA, policy logic was scattered across applications, scripts, and API gateways: No Unified Standard: Every programming language (Go, Python, Java, Node.js) handled authorization differently. Audit & Compliance Nightmares: Proving to security auditors that all services enforce the same compliance rules required digging through thousands of lines of application code. High Deployment Risk: Changing a simple access rule required modifying application source code and triggering a full CI/CD deployment pipeline. Key Benefits of OPA Single Sour

## Keycloak 26.8.0 released

DevFeed: [Keycloak 26.8.0 released](<https://devfeed.tech/articles/keycloak-26-8-0-released-63151.md>)

Original publisher: [Read original article](<https://www.keycloak.org/2026/10/keycloak-2680-released>)

Author: Keycloak Team

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

Content type: release

Language: en

Sources: [Keycloak Blog](<https://devfeed.tech/sources/keycloak-blog.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [API](<https://devfeed.tech/topics/api.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [HTTP](<https://devfeed.tech/topics/http.md>)

Tags: [certificate](<https://devfeed.tech/tags/certificate.md>), [consent](<https://devfeed.tech/tags/consent.md>), [credential-management](<https://devfeed.tech/tags/credential-management.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [idm](<https://devfeed.tech/tags/idm.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [keycloak-release](<https://devfeed.tech/tags/keycloak-release.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [saml](<https://devfeed.tech/tags/saml.md>), [security](<https://devfeed.tech/tags/security.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

Keycloak 26.8.0 adds support for SCIM provisioning, stateless multi-cluster deployments, credential issuance and verification, and client secret rotation. The release also introduces preview token delegation for applications such as AI agents, with consent controls and fine-grained authorization.

### Source excerpt

To download the release go to Keycloak downloads. Highlights This release features new capabilities for users and administrators of Keycloak. The highlights of this release are: Issue and verify digital wallet credentials with OID4VCI and OID4VP Automate user provisioning across identity systems with the SCIM API Run multi-cluster deployments without an external cache using stateless mode (now supported) Simpler administration with automatic index creation, reduced memory usage, and enhanced HTTP performance Token exchange delegation for AI agents and automation with consent and FGAP authorization Read on to learn more about each new feature. If you are upgrading from a previous release, also review the changes listed in the upgrading guide. Security and Standards Verifiable Credential Issuance promoted to preview with credential management and revocation The OpenID for Verifiable Credential Issuance (OID4VCI) feature has been promoted from experimental to preview. It can now be enabled with --features=preview or --features=oid4vc-vci. Credential lifecycle management now includes revocation when refresh tokens are revoked, and a new Application Initiated Action (AIA) lets users request credential issuance within an authenticated session. Key attestation is configurable in the admin console with hardened x5c certificate validation following the HAIP profile. This release also adds experimental support for the mdoc format, provided by the new experimental feature oid4vc-mdoc. Integration guides for the Lissi and Valera wallets are available, along with documentation for SD-JWT signing key setup, credential management, and revocation. Example applications are provided in this release (for illustration, not officially supported): Quickstart OID4VCI deployment - a playground for rapid prototyping with mdoc and SD-JWT credentials OID4VCI Demo in Keycloak FAPI playground - available to show the details of the OID4VCI protocol messages exchanged between wallet and issuer, a

## Meta's ZGateway Cuts ZippyDB Connections 19x While Handling 1B+ Operations per Second

DevFeed: [Meta's ZGateway Cuts ZippyDB Connections 19x While Handling 1B+ Operations per Second](<https://devfeed.tech/articles/meta-s-zgateway-cuts-zippydb-connections-19x-while-handling-1b-operations-per-second-60813.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/meta-zgateway-zippydb-proxy/>)

Author: Leela Kumili

Published: 2026-09-28T13:55:00Z

Content type: news

Language: en

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

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>)

Tags: [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [availability](<https://devfeed.tech/tags/availability.md>), [caching](<https://devfeed.tech/tags/caching.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [database](<https://devfeed.tech/tags/database.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [fault-tolerance](<https://devfeed.tech/tags/fault-tolerance.md>), [key-value-store](<https://devfeed.tech/tags/key-value-store.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [meta-zgateway-zippydb-proxy](<https://devfeed.tech/tags/meta-zgateway-zippydb-proxy.md>), [multi-region](<https://devfeed.tech/tags/multi-region.md>), [news](<https://devfeed.tech/tags/news.md>), [reduction](<https://devfeed.tech/tags/reduction.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>)

### AI overview

Meta introduced ZGateway, a stateless proxy layer for its ZippyDB distributed key-value store, to reduce connection and reliability problems caused by a large client fleet. The gateway handles more than 1 billion operations per second and about 40% of ZippyDB traffic; Meta estimates it reduces persistent connections by roughly 19 times. It centralizes traffic management functions such as shard resolution, caching, admission control, and request batching.

### Source excerpt

Meta has introduced ZGateway, a stateless proxy for ZippyDB that centralizes connection management, traffic routing, caching, load balancing, and admission control. The gateway handles more than 1 billion operations per second and about 40% of ZippyDB traffic, while Meta's model estimates a 19x reduction in persistent connections. By Leela Kumili

## The rise of agentic AI in Kubernetes management

DevFeed: [The rise of agentic AI in Kubernetes management](<https://devfeed.tech/articles/the-rise-of-agentic-ai-on-kubernetes-unleashing-the-new-infrastructure-layer-60542.md>)

Original publisher: [Read original article](<https://thenewstack.io/agentic-ai-kubernetes-management/>)

Author: Rhys Oxenham

Published: 2026-09-27T14:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Overview, News and Trends | The New Stack](<https://devfeed.tech/sources/kubernetes-overview-news-and-trends-the-new-stack.md>), [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [platform-teams](<https://devfeed.tech/tags/platform-teams.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [sponsor-suse](<https://devfeed.tech/tags/sponsor-suse.md>), [sponsored](<https://devfeed.tech/tags/sponsored.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>), [suse](<https://devfeed.tech/tags/suse.md>)

### AI overview

Agentic AI is being applied to Kubernetes and multi-cluster operations as infrastructure workloads and operational demands grow. These systems can observe, reason, and act within set limits, but their usefulness depends on access to cluster state, policies, and rules. Clear boundaries between observation, recommendations, and changes can help platform teams gain speed while retaining control.

### Source excerpt

AI is changing expectations around infrastructure and operations, including Kubernetes management. When models run close to the data they use, The post The rise of agentic AI on Kubernetes: unleashing the new infrastructure layer appeared first on The New Stack.

## How eBPF and OpenTelemetry Reveal a Payment Service Regression

DevFeed: [How eBPF and OpenTelemetry Reveal a Payment Service Regression](<https://devfeed.tech/articles/how-ebpf-enriches-otel-a-payment-service-quietly-regressing-after-an-unsuccessful-migration-79994.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/ebpf-otel-payment-service-regression>)

Author: Anais Dotis

Published: 2026-09-22T17:13:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [eBPF](<https://devfeed.tech/topics/ebpf.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [expand and contract migration](<https://devfeed.tech/topics/expand-and-contract-migration.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>)

Tags: [ebpf](<https://devfeed.tech/tags/ebpf.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [otel](<https://devfeed.tech/tags/otel.md>), [payment](<https://devfeed.tech/tags/payment.md>)

### AI overview

The article demonstrates how eBPF payload capture, OpenTelemetry traces, and Kubernetes configuration diffs helped investigate a payment service regression after a migration. It also describes eBPF's limits for identifying application functions without symbols and frame pointers.

### Source excerpt

Explore how eBPF payload capture and Kubernetes config diffs reveal payment service regressions and failed migrations that traditional APM tracing misses.

## RFC 9842 for Microservices: It Depends

DevFeed: [RFC 9842 for Microservices: It Depends](<https://devfeed.tech/articles/rfc-9842-for-microservices-it-depends-55614.md>)

Original publisher: [Read original article](<https://dfa1.github.io/articles/rfc-9842-for-microservices.html>)

Author: Davide Angelocola

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

Content type: comparison

Language: en

Sources: [Davide Angelocola](<https://devfeed.tech/sources/davide-angelocola.md>)

Topics: [Compression](<https://devfeed.tech/topics/compression.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>)

Tags: [compression](<https://devfeed.tech/tags/compression.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [http](<https://devfeed.tech/tags/http.md>), [latency](<https://devfeed.tech/tags/latency.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [migration](<https://devfeed.tech/tags/migration.md>), [sdks](<https://devfeed.tech/tags/sdks.md>)

### AI overview

The article examines RFC 9842's compression dictionary negotiation for HTTP services, especially microservices and public APIs. It compares shared-dictionary compression with changing payload formats over gRPC, and discusses tradeoffs involving latency, deployment coordination, client control, and dictionary rotation.

### Source excerpt

RFC 9842 -- Compression Dictionary Transport, published September 2025 -- lets HTTP clients and servers negotiate a shared compression dictionary, then compress responses against it (dcb for Brotli, dcz for Zstandard). It was written with browsers in mind: the spec's two motivating use cases (§1.1) are a delta-compressed JS bundle against the previous version, and a dictionary of common HTML/template boilerplate shared across pages.

## Building a data plane from scratch: Stripe's own high-performance distributed proxy

DevFeed: [Building a data plane from scratch: Stripe's own high-performance distributed proxy](<https://devfeed.tech/articles/building-a-data-plane-from-scratch-stripe-s-own-high-performance-distributed-proxy-81737.md>)

Original publisher: [Read original article](<https://stripe.dev/blog/building-a-data-plane-from-scratch-stripes-own-high-performance-distributed-proxy>)

Author: Jack Loughran

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

Content type: article

Language: en

Sources: [Stripe Dot Dev Blog](<https://devfeed.tech/sources/stripe-dot-dev-blog.md>)

Topics: [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>)

Tags: [distributed](<https://devfeed.tech/tags/distributed.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [performance](<https://devfeed.tech/tags/performance.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>)

### AI overview

Stripe's infrastructure team replaced Envoy with an alternative service-mesh architecture as traffic growth strained the system and the company aimed to maintain 99.9995% reliability.

### Source excerpt

To minimize failed payments for our users, Stripe targets 99.9995% reliability. As traffic grew beyond 1.6% of global GDP, this put intense strain on the service mesh. This is the story of the infrastructure team replacing Envoy, a popular solution, with an alternative architecture.

## Shadow Deployment: How It Works, And Key Considerations

DevFeed: [Shadow Deployment: How It Works, And Key Considerations](<https://devfeed.tech/articles/shadow-deployment-how-it-works-and-key-considerations-51078.md>)

Original publisher: [Read original article](<https://www.portainer.io/blog/shadow-deployment>)

Author: Portainer Team

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

Content type: tutorial

Language: en

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

Topics: [Deployment](<https://devfeed.tech/topics/deployment.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [gateway-load-balancer](<https://devfeed.tech/tags/gateway-load-balancer.md>), [latency](<https://devfeed.tech/tags/latency.md>), [logging](<https://devfeed.tech/tags/logging.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [production](<https://devfeed.tech/tags/production.md>), [regression](<https://devfeed.tech/tags/regression.md>), [release](<https://devfeed.tech/tags/release.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

This guide explains shadow deployment, a release strategy in which a new service version processes mirrored production traffic without serving responses to users. It covers the architecture, benefits, challenges, and considerations for observing regressions before release.

### Source excerpt

Shadow deployment is a release strategy where a new version runs alongside production and processes mirrored traffic without serving responses to users.

## 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

[Next page](<https://devfeed.tech/topics/service-mesh.md?cursor=WyIyMDI2LTAzLTI3VDAwOjAwOjAwKzAwOjAwIiwgIjIzZjA1YTk0LTIwZGYtNDA2Yy1hMjlkLWZhNDE2NWY1OWIxMyJd>)