Istio came with its new version recently. It is a minor release, but it contains some significant changes and fixes. In this article, we will have a detailed look at what version 1.11.3 brings to the table.
So, without wasting any time. Let’s start!
What is Istio?
Istio is a CNCF project and is an open platform for providing a uniform way to integrate microservices. It manages traffic flow across microservices, enforce policies and aggregate telemetry data. Istio has a control plane that provides an abstraction layer over the underlying cluster management platform, namely Kubernetes.
This release didn’t get many features, but we can see that one feature got an addition in version 1.11.3. We see the addition of values to the Istio Gateway Helm charts for configuring annotations on the ServiceAccount. We can use it to enable IAM Roles for Service Accounts on AWS EKS.
Only one enhancement got a placing in this latest release. Through this update, we can see the updating of the platform to allow specifying NICs that bypassing traffic capture in Istio iptables.
Bugs and other fixes
This update stressed the fixing of bugs and other problems. As a result of which, we can see some bugs got fixed with its release.
Firstly, we can see the fixing of the istioctl analyze command to not output [IST0132] message when analyzing the gateway of the virtual service. Again, we see the fixing of the bug, which uses a Service’s pointer address to get its instances in the case where a sidecar’s egress listener has a port. Another bug in the “image: auto” analyzer got a fixing where it was causing the analyzer to fail to take into account the Deployment namespace.
We also see fixing the istioctl x workload command output to set the correct discoveryAddress for revisioned control planes. There is also fixing the gateway analyzer message reporting if there is no selector in the gateway spec. Furthermore, we see the issue which was causing the memory to not operate freely after the disconnection of XDS clients gets a fixing. Finally, we observe the fix of the issue, which occurred when multiple VirtualServices with the same name existed in different namespaces.
In this article, we have covered the various changes that Istio brings with version 1.11.3. Though it is a minor update, the bug fixes are noteworthy because they will help users have a smooth experience while using the platform. Get a taste of this new and updated Istio by clicking here. Contribute to this open-source project by clicking here. Get your hands dirty with integrating microservices with the help of Istio, and I will see you all in the next one.
Read more of our exciting blogs below, and happy learning!