• Maintain an active OpenShift Dedicated subscription on your Red Hat account. If you do not have a subscription, contact your sales representative for more information.

  • Install the version of the OpenShift Dedicated command line utility (the oc client tool) that matches your OpenShift Dedicated version and add it to your path.

For additional information about Red Hat OpenShift Service Mesh lifecycle and supported platforms, refer to the Support Policy.

Supported configurations

The following configurations are supported for the current release of Red Hat OpenShift Service Mesh.

Supported platforms

The Red Hat OpenShift Service Mesh Operator supports multiple versions of the ServiceMeshControlPlane resource. Version 2.5 Service Mesh control planes are supported on the following platform versions:

  • Red Hat OpenShift Container Platform version 4.10 or later

  • Red Hat OpenShift Dedicated version 4

  • Azure Red Hat OpenShift (ARO) version 4

  • Red Hat OpenShift Service on AWS (ROSA)

Unsupported configurations

Explicitly unsupported cases include:

  • OpenShift Online is not supported for Red Hat OpenShift Service Mesh.

  • Red Hat OpenShift Service Mesh does not support the management of microservices outside the cluster where Service Mesh is running.

Supported network configurations

Red Hat OpenShift Service Mesh supports the following network configurations.

  • OpenShift-SDN

  • OVN-Kubernetes is available on all supported versions of OpenShift Dedicated.

  • Third-Party Container Network Interface (CNI) plugins that have been certified on OpenShift Dedicated and passed Service Mesh conformance testing. See Certified OpenShift CNI Plug-ins for more information.

Supported configurations for Service Mesh

  • This release of Red Hat OpenShift Service Mesh is only available on OpenShift Dedicated x86_64, IBM Z®, and IBM Power®.

    • IBM Z® is only supported on OpenShift Dedicated 4.10 and later.

    • IBM Power® is only supported on OpenShift Dedicated 4.10 and later.

  • Configurations where all Service Mesh components are contained within a single OpenShift Dedicated cluster.

  • Configurations that do not integrate external services such as virtual machines.

  • Red Hat OpenShift Service Mesh does not support EnvoyFilter configuration except where explicitly documented.

Supported configurations for Kiali

  • The Kiali console is only supported on the two most recent releases of the Google Chrome, Microsoft Edge, Mozilla Firefox, or Apple Safari browsers.

  • The openshift authentication strategy is the only supported authentication configuration when Kiali is deployed with Red Hat OpenShift Service Mesh (OSSM). The openshift strategy controls access based on the individual’s role-based access control (RBAC) roles of the OpenShift Dedicated.

Supported configurations for Distributed Tracing

  • Jaeger agent as a sidecar is the only supported configuration for Jaeger. Jaeger as a daemonset is not supported for multitenant installations or OpenShift Dedicated.

Supported WebAssembly module

  • 3scale WebAssembly is the only provided WebAssembly module. You can create custom WebAssembly modules.

Next steps