This is a cache of https://docs.openshift.com/container-platform/4.12/service_mesh/v1x/preparing-ossm-installation.html. It is a snapshot of the page at 2024-11-20T13:13:08.749+0000.
Preparing to install <strong>service</strong> Mesh - <strong>service</strong> Mesh 1.x | <strong>service</strong> Mesh | OpenShift Container Platform 4.12
  1. Documentation
    2. history bug_report picture_as_pdf
×

Preparing to install service Mesh

You are viewing documentation for a Red Hat OpenShift service Mesh release that is no longer supported.

service Mesh version 1.0 and 1.1 control planes are no longer supported. For information about upgrading your service mesh control plane, see Upgrading service Mesh.

For information about the support status of a particular Red Hat OpenShift service Mesh release, see the Product lifecycle page.

Before you can install Red Hat OpenShift service Mesh, review the installation activities, ensure that you meet the prerequisites:

Prerequisites

Red Hat OpenShift service Mesh supported configurations

The following are the only supported configurations for the Red Hat OpenShift service Mesh:

  • OpenShift Container Platform version 4.6 or later.

OpenShift Online and Red Hat OpenShift Dedicated are not supported for Red Hat OpenShift service Mesh.

  • The deployment must be contained within a single OpenShift Container Platform cluster that is not federated.

  • This release of Red Hat OpenShift service Mesh is only available on OpenShift Container Platform x86_64.

  • This release only supports configurations where all service Mesh components are contained in the OpenShift Container Platform cluster in which it operates. It does not support management of microservices that reside outside of the cluster, or in a multi-cluster scenario.

  • This release only supports configurations that do not integrate external services such as virtual machines.

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

Supported configurations for Kiali on Red Hat OpenShift service Mesh

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

Supported Mixer adapters

  • This release only supports the following Mixer adapter:

    • 3scale Istio Adapter

service Mesh Operators overview

Red Hat OpenShift service Mesh requires the use of the Red Hat OpenShift service Mesh Operator which allows you to connect, secure, control, and observe the microservices that comprise your applications. You can also install other Operators to enhance your service mesh experience.

Do not install Community versions of the Operators. Community Operators are not supported.

The following Operator is required:

Red Hat OpenShift service Mesh Operator

Allows you to connect, secure, control, and observe the microservices that comprise your applications. It also defines and monitors the serviceMeshControlPlane resources that manage the deployment, updating, and deletion of the service Mesh components. It is based on the open source Istio project.

The following Operators are optional:

Kiali Operator provided by Red Hat

Provides observability for your service mesh. You can view configurations, monitor traffic, and analyze traces in a single console. It is based on the open source Kiali project.

Red Hat OpenShift distributed tracing platform (Tempo)

Provides distributed tracing to monitor and troubleshoot transactions in complex distributed systems. It is based on the open source Grafana Tempo project.

The following optional Operators are deprecated:

Starting with Red Hat OpenShift service Mesh 2.5, Red Hat OpenShift distributed tracing platform (Jaeger) and OpenShift Elasticsearch Operator are deprecated and will be removed in a future release. Red Hat will provide bug fixes and support for these features during the current release lifecycle, but these features will no longer receive enhancements and will be removed. As an alternative to Red Hat OpenShift distributed tracing platform (Jaeger), you can use Red Hat OpenShift distributed tracing platform (Tempo) instead.
Red Hat OpenShift distributed tracing platform (Jaeger)

Provides distributed tracing to monitor and troubleshoot transactions in complex distributed systems. It is based on the open source Jaeger project.

OpenShift Elasticsearch Operator

Provides database storage for tracing and logging with the distributed tracing platform (Jaeger). It is based on the open source Elasticsearch project.

See Configuring the Elasticsearch log store for details on configuring the default Jaeger parameters for Elasticsearch in a production environment.

Next steps