Service mesh: istiio 1.8 sets besides security on more usability

Service Mesh: Istiio 1.8 sets in addition to security on more usability

The istio team published the fourth and last release in 2020 the service mesh platform. With istio 1.8 if the developer team goes another step towards multi-cluster meshes and workloads running on vitual maschines (vm) in mesh. The main focus of the update lies according to release notes on troubleshooting and improving the platform.

Itio 1.8 brings with an installation instructions for developers, which should make it easier for you to install a mesh that extends several clusters. Developers can decide whether the clusters should be in the same network and whether multiple control levels are required.

Vm support and security

The itio team has set itself the goal for the year 2020 to expand the support for workloads on kubernetes. With istio 1.6 team took the first step in this way. With the api workloadloading try in version 1.7 should not be easier to present on kubernetes-based workloads in itio. For this, virtual machines (vms) or bare metal workloads were lifted on the same level as a kubernetes pod. Developers can define a service that is supported by vms in addition to the pods. In this way, vm workloads can be migrated to a kubernetes cluster without interrupting traffic from and to this.

Building on the safety precautions in version 1.7, the current release sets the focus on the user-friendliness. In addition to simplifying the installation process, developer can use the istiotl analysis tool for installation. A new dns proxy feature allows vms mesh services to be erosed from vms – without an insecure query with the cluster dns server. The new feature should reduce cluster dns traffic and the number of look-ups that are necessary to dissolve the ip of a service. By automatic registration, it is possible to inform the vm agents about the type of workload, and automatically create workload entry objects for him when the agent join the mesh.

Itio 1.8 stop further innovations for safety. For example, now isiod certificates send to gatways instead of reading them directly from kubernetes. Cleaner information about itio 1.8 can be found in the release notes.

Leave a Comment