After eight months Istio 1.1 has finally been released. Called Enterprise Ready, the release focuses on performance and scalability. We will also share more of Istio’s production practices this year. The Chinese language support on the official website is also very friendly, and the ServiceMesher community has accumulated a wealth of learning materials →www.servicemesher.com

IO/en /blog/201… I translated it.

Istio 1.1 was released today at 4am Beijing time and 1pm Pacific time.

Since the 1.0 release last July, we’ve done a lot of work to help people get Istio into production. As expected, we released a lot of patches (6 so far!). But we are also working hard to add new features to the product.

The theme for version 1.1 is “Enterprise Ready.” It’s good to see more companies using Istio in production, but Istio has hit a few bottlenecks as larger companies have come in.

Our main areas of focus include performance and scalability. As people move Istio into production and use larger clusters to run more services at higher capacity, they may encounter some scaling and performance issues. Sidecar takes up too many resources and adds too much latency. The control plane (Pilot in particular) consumes excessive resources.

We put a lot of effort into making the data plane and the control plane more efficient. In performance testing for 1.1, we observed that sidecar typically required 0.5 Vcpus to process 1000 RPS. A single Pilot instance can handle 1,000 services (and 2,000 pods) and consume 1.5 vcpus and 2GB of memory. Sidecar increases by 5 milliseconds at the 50th percentile and by 10 milliseconds at the 99th percentile (executing the policy will increase latency).

We’ve also finished working on namespace isolation. You can use the Kubernetes namespace to enforce control boundaries to ensure that teams do not interfere with each other.

We also improved multi-clustering capabilities and usability. We listened to the community and improved the default Settings for traffic control and policy. We introduced a new component called Galley. Galley verifies the YAML configuration, reducing the possibility of configuration errors. Galley is also used in multi-cluster setups — gathering service discovery information from each Kubernetes cluster. We also support other multi-cluster topologies, including single control plane and multiple synchronous control planes, without flat network support.

See the release notes for more information and details.

There is more to come. It is well known that Istio has many moving parts that do too much work. In order to solve this problem, we recently formed the Usability Working Group. There’s a lot going on in the community meeting (Thursday at 11 a.m.) and in the task force. You can use GitHub credentials to log in to discuss.istio. IO to join the discussion!

Thanks to everyone who has contributed to Istio over the past few months – tinkering with 1.0, adding features to 1.1, and the recent extensive testing on 1.1. Special thanks to those companies and customers who worked with us to install and upgrade to earlier versions, helping us spot issues prior to release.

Finally, go to the latest documentation and install version 1.1. Happy meshing!

The official website

The ServiceMesher community has been maintaining the Chinese pages of Istio official documents since Istio 0.6 release. As of 12 PM March 19, 2019, there are 596 PR amalgamations and a total of more than 310 documents have been maintained. Thank you for your efforts! Some documents may be slightly behind the English version, synchronization work is ongoing, to participate please visit github.com/servicemesh… There is a language switch button on the right side of each page of Istio website. You can switch between Chinese and English versions at any time, and you can submit documents for modification or report bugs on the website.

Other information

Istio handbook

In the name of the community, the open source e-book Istio Handbook — Istio Service Grid Advanced Combat was launched. ServiceMesher community, as one of the earliest open source communities in China to research and promote ServiceMesh technology, decided to integrate community resources. Co-write an open source ebook as a service grid think tank.

GitHub address: github.com/servicemesh…

Online browsing address: www.servicemesher.com/istio-handb…

Istio Knowledge graph

The Istio knowledge Graph is a knowledge structure map in the Istio ServiceMesh compiled by members of the ServiceMesher community.

Istio Knowledge Graph GitHub address: github.com/servicemesh…

ServiceMesher community site

The ServiceMesher community website, www.servicemesher.com, is a one-stop portal for you to learn about ServiceMesh and participate in the community, with technical articles and timely updates on ServiceMesh.