The service mesh consul developed by Hashicorp is now in version 1.9. The developers have concentrated in the new release to providing an apparently granular control of service meshes, the revision of the monitoring of services within the service mesh and tighter integrations with more Runtime platforms on Kubernetes-Native Way.
An overview of the most important changes
Consul 1.9 Contains below other functions:
- The extension of the Intention Model For so-called Application-Aware (Layer 7) Intentions should provide the possibility of creating guidelines that also evaluates information on the application level in addition to the service identity.
- The Service Mesh Visualization offers a new topology tab in the consul user interface with topology diagrams and service mesh metrics. These functions should improve the configuration and troubleshooting in service mesh.
- With the new version, ConSul can be configured by objects in Kubernetes style. It is also offered to manage the service mesh configuration for services via CRDS (Custom Resource Definition).
- It is now possible to install Consul via Helm Charts in OpensShift.
- The Active Health Checks for Consul On Kubernetes integrates KUBERNETES status conversions in Consul. This should ensure that traffic is not forwarded to faulty pods.
- Consul can now deal with streaming. This is considered significant improvement in the task of how update notifications for blocking queries within the cluster are delivered. Streaming is intended to reduce the CPU and bandwidth usage of the network to Consul servers in extensive implementations.
If you like deeper into the innovations, you are well advised with the blog envision. The changelog lists the changes in a small part.
The ability of a service mesh to simplify complex containers and improve network functions makes technology an important infrastructure level. In a service mesh, each service instance is coupled to that of a reverse proxy server. The service instance and the Sidecar proxy share a container, which in turn manages from a container orchestration tool. The service proxies are responsible for communication with other service instances and can support functions such as service detection, load balancing, authentication and authorization and secure communication.
In the service mesh, the service instances and your Sidecar proxy form the data level, which also fell in processing and answering inquiries. Service mesh also includes a level for controlling the interaction between the services that is conveyed by its Sidecar proxies.