Migration to Kubernetes and Linux-infrastructure during the digital transformation of organizations leads to the fact that applications are increasingly being built on the basis of microservice architecture and, as a result, very often become overgrown with complex request routing schemes between services.
With Red Hat OpenShift Service Mesh, we go beyond traditional routing and provide components for tracing and visualizing such requests to make service interaction simpler and more reliable. Introduction of a special logical control level, the so-called service grid , helps simplify connectivity, control, and operational management on a per-application basis deployed on Red Hat OpenShift, the leading enterprise-class Kubernetes platform.
Red Hat OpenShift Service Mesh is offered as a custom Kubernetes operator that you can try out in Red Hat OpenShift 4 .
Improved tracking, routing and optimization of communications at the application and service level
Using only hardware load balancers, specialized network equipment and other similar solutions that have become the norm in today's IT environments, it is very difficult, and sometimes impossible, to consistently and uniformly regulate and manage the service-to-service communications that arise. between applications and their services. With the advent of an additional layer of service mesh control, containerized applications can better track, route, and optimize their communications with Kubernetes as the core of the platform. The service mesh helps simplify the management of hybrid workloads with multiple locations and more granular control over the location of data. With the release of the OpenShift Service Mesh, we hope this important component of the microservice technology stack will empower organizations to implement multi-cloud and hybrid strategies.
The OpenShift Service Mesh is built on top of several open source projects such as Istio, Kiali and Jaeger and provides the ability to program communication logic within a microservice application architecture. As a result, development teams can focus entirely on developing applications and services that solve business problems.
Making life easier for developers
, before the advent of the service mesh, a huge part of the work of managing complex interactions between services fell on the shoulders of application developers. Under these conditions, they need a whole range of tools for managing the application life cycle, from controlling the results of code deployment to managing application traffic in production. For an application to work successfully, all of its services must communicate with each other normally. Tracing allows the developer to track how each service interacts with the rest of the functions and helps to identify bottlenecks that create unnecessary delays in real work.
The ability to visualize the relationships between all services and see the topology of interaction also helps to better understand the complex picture of inter-service relationships. By combining these useful features within the OpenShift Service Mesh, Red Hat provides the developer with an extended set of tools needed to successfully develop and deploy cloud microservices.
To simplify the creation of a service mesh, our solution makes it easy to implement this level of control within an existing OpenShift instance using the appropriate Kubernetes operator. This operator takes care of installation, network integration, and operational management of all the necessary components, which allows you to immediately start using the newly created service mesh for deploying real applications.
Reducing the effort required to implement and manage a service mesh allows you to build and test application concepts faster and stay in control as they evolve. Why wait until inter-service communication management becomes a real problem? OpenShift Service Mesh easily provides the scalability you need before you actually need it.
The list of benefits that OpenShift Service Mesh brings to OpenShift users includes:
- Tracing and monitoring (Jaeger). Activating a service mesh to improve manageability can come with some performance degradation, so OpenShift Service Mesh can measure a baseline of performance and then use that data for further optimization.
- Visualization (Kiali). A visual representation of the service mesh helps to understand the topology of the service mesh and the overall picture of interacting services.
- Kubernetes Service Mesh Operator. Minimizes the need for administration in managing applications by automating common tasks such as installation, maintenance, and service lifecycle management. By adding business logic, you can further simplify management and speed up the introduction of new features in production. The OpenShift Service Mesh operator deploys the Istio, Kiali and Jaeger packages, complete with configuration logic that implements all the required functionality at once.
- Support for multiple network interfaces (multus). OpenShift Service Mesh eliminates manual operations and gives the developer the ability to run code in enhanced security mode using SCC (Security Context Constraint). In particular, additional isolation of workloads in a cluster is provided, for example, for a namespace, you can specify which workloads can run as root and which cannot. As a result, it is possible to combine the advantages of Istio, which are much sought after by developers, with the well-defined security measures that cluster administrators need.
- Integration with Red Hat 3scale API Management. For developers or IT operators who need increased security access to service APIs, OpenShift Service Mesh offers a standard Red Hat 3scale Istio Mixer Adapter component, which, unlike a service mesh, allows you to control inter-service communications at the API level.
As for the further development of service mesh technologies, earlier this year Red Hat announced its participation in an industry project , which aims to increase the interoperability of these technologies offered by various vendors. Collaborating on this project will help us provide Red Hat OpenShift users with greater and more flexible choices, and usher in a new era where we can offer developers "NoOps" environments.
Try OpenShift
Service mesh technologies help to greatly simplify the use of microservice stacks in a hybrid cloud. Therefore, we encourage everyone who actively uses Kubernetes and containers to .
Source: habr.com
