About OpenShift service Mesh - service Mesh 2.x | service Mesh

Introduction to Red Hat OpenShift service Mesh
Core features

Because Red Hat OpenShift service Mesh releases on a different cadence from OpenShift Container Platform and because the Red Hat OpenShift service Mesh Operator supports deploying multiple versions of the serviceMeshControlPlane, the service Mesh documentation does not maintain separate documentation sets for minor versions of the product. The current documentation set applies to the most recent version of service Mesh unless version-specific limitations are called out in a particular topic or for a particular feature.

For additional information about the Red Hat OpenShift service Mesh life cycle and supported platforms, refer to the Platform Life Cycle Policy.

Introduction to Red Hat OpenShift service Mesh

Red Hat OpenShift service Mesh addresses a variety of problems in a microservice architecture by creating a centralized point of control in an application. It adds a transparent layer on existing distributed applications without requiring any changes to the application code.

Microservice architectures split the work of enterprise applications into modular services, which can make scaling and maintenance easier. However, as an enterprise application built on a microservice architecture grows in size and complexity, it becomes difficult to understand and manage. service Mesh can address those architecture problems by capturing or intercepting traffic between services and can modify, redirect, or create new requests to other services.

service Mesh, which is based on the open source Istio project, provides an easy way to create a network of deployed services that provides discovery, load balancing, service-to-service authentication, failure recovery, metrics, and monitoring. A service mesh also provides more complex operational functionality, including A/B testing, canary releases, access control, and end-to-end authentication.

Core features

Red Hat OpenShift service Mesh provides a number of key capabilities uniformly across a network of services:

Traffic Management - Control the flow of traffic and API calls between services, make calls more reliable, and make the network more robust in the face of adverse conditions.
service Identity and Security - Provide services in the mesh with a verifiable identity and provide the ability to protect service traffic as it flows over networks of varying degrees of trustworthiness.
Policy Enforcement - Apply organizational policy to the interaction between services, ensure access policies are enforced and resources are fairly distributed among consumers. Policy changes are made by configuring the mesh, not by changing application code.
Telemetry - Gain understanding of the dependencies between services and the nature and flow of traffic between them, providing the ability to quickly identify issues.