live wire
▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer
upstreambeat.ai
releasePLATFORM

OpenShift Service Mesh 3.4 adds nftables, FIPS 140-3 and inference routing

The release prepares meshes for RHEL 10, expands Gateway API support and gives operators a path to mix sidecar and ambient workloads.

Service Mesh compares legacy traffic handling with nftables and AI routing.
AI-generated illustration
By The News Desk· Sep 21, 2026the quick take — two AI hosts go live when you do

Red Hat OpenShift Service Mesh 3.4 is generally available for OpenShift Container Platform 4.20 and later, with changes aimed at the RHEL 10 transition, stricter compliance requirements and newer traffic-management patterns. The release notes also add a direct bridge to AI-serving infrastructure through Gateway API Inference Extension support.

What changed

Service Mesh 3.4 introduces native nftables support for both sidecar and ambient modes. That matters because RHEL 10 and RHEL CoreOS 10 remove the legacy iptables framework that the mesh previously used to redirect traffic through proxies. Operators must enable values.global.nativeNftables=true when installing or updating the control plane; ambient-mode nodes may also require a reboot during migration, according to the Red Hat documentation.

The release also supports FIPS 140-3 on FIPS-enabled OpenShift clusters in sidecar and ambient modes. Red Hat says this maintains compliance as FIPS 140-2 expires on September 21, 2026, and adds TLS 1.3 for mesh traffic while retaining TLS 1.2 as the minimum version. The same release notes describe coexistence of sidecar and ambient workloads in separate namespaces, providing an incremental migration path where ambient mode does not yet cover every workload.

Why AI platform teams should notice

Service Mesh 3.4 supports Gateway API 1.5.1, including stable ListenerSet, TLSRoute, HTTPRoute CORS, client-certificate validation and multi-domain certificate selection. It also supports Gateway API Inference Extension 1.4.0 for routing and load balancing across GPU-backed model-serving workloads, tying the mesh release directly to OpenShift AI deployment patterns documented by Red Hat.

Several defaults change beneath those headline features. Debug-endpoint authorization is enabled by default, Envoy metrics compression is enabled by default, and ambient workloads now use DNS proxying by default. Existing ambient pods do not automatically pick up the new DNS redirection after an upgrade; Red Hat says operators must restart those pods or configure Istio CNI reconciliation at startup. Circuit-breaker metrics tracking is disabled by default to reduce proxy memory use, with an environment variable available to restore it.

What operators should do

Before upgrading, platform teams should verify that their OpenShift version supports Service Mesh 3.4, decide whether their RHEL 10 transition requires native nftables, and test tools that depend on Istio debug endpoints. Teams adopting ambient mode should plan for pod restarts and review the documented coexistence limitations. AI platform teams can separately evaluate whether Inference Extension routing should replace bespoke gateway logic for model endpoints. Those checks follow directly from the configuration and compatibility changes in the 3.4 release notes.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk