English edition · cyberattaques.org in FrenchFrançais
IT news

Red Hat OpenShift Service Mesh 3.5 released with Istio 1.31 and multicluster ambient mode

Red Hat has made OpenShift Service Mesh 3.5 generally available, shipping Istio 1.31 and Kiali 2.33 and supporting OpenShift Container Platform 4.20 and later. Teams running a service mesh on OpenShift are concerned, particularly those looking at ambient mode or workload identity.

What to do now Illustration photo (container cluster network)

Red Hat has announced general availability of OpenShift Service Mesh 3.5, the service mesh it ships with OpenShift Container Platform. The product is built on the open source Istio, Envoy and Kiali projects.

The release moves Istio to version 1.31 and the Kiali observability console to version 2.33. Red Hat says it also brings a substantial set of enhancements from Istio 1.31, though the announcement summary does not list them.

Service Mesh 3.5 is supported on OpenShift Container Platform 4.20 and later, including Red Hat OpenShift 5.0. Clusters still on a release older than 4.20 will need to be upgraded first.

Three capabilities reach general availability: multicluster deployments in ambient mode, dual-stack IPv4/IPv6 in ambient mode, and Red Hat's zero trust workload identity manager, based on SPIRE, in sidecar mode. General availability means these features can now be considered for production use with vendor support.

The source does not mention end-of-support dates for earlier Service Mesh versions, nor any security fixes tied to this release.

Action plan

What to do now

  1. Confirm your clusters run OpenShift Container Platform 4.20 or later before scheduling a move to Service Mesh 3.5.
  2. Review the Istio 1.31 and Kiali 2.33 release notes for changes that could affect your existing mesh configuration.
  3. Assess whether multicluster ambient mode, dual-stack IPv4/IPv6 or the SPIRE-based workload identity manager fit your architecture plans.
  4. As general good practice, test the upgrade in a staging environment before rolling it out to production.

Sources