Shulou(Shulou.com)05/31 Report--

This article introduces the knowledge of "what functions have been added to Istio 1.8". In the operation of actual cases, many people will encounter such a dilemma. Then let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Istio 1.8, the last release of Istio in 2020, continues to move forward in accordance with the goals set by the Istio community at the beginning of this year, with the following updates:

Support for installation and upgrade using Helm 3

Mixer has been officially removed

Istio DNS proxy is added to intercept the DNS query of the application transparently and realize the intelligent response.

WorkloadGroup has been added to simplify the introduction of virtual machines

WorkloadGroup is a new API object designed to be used with non-Kubernetes workloads such as virtual machines to mimic the existing sidecar injection and deployment specification model for Kubernetes workloads to guide Istio agents.

Installation and upgrade

Istio abandoned Helm from version 1.5, installed it with istioctl manifest, and later changed it to istioctl install. Now it has returned to Helm,Helm as the most commonly used application installation management component in Kubernetes environment. This return is also a response to listening to users' voices and optimizing the installation experience. However, Istio Operator will still be the final form of Istio installation. From version 1.8, Istio supports in-place upgrade and canary upgrade using Helm.

Enhance the ease of use of Istio

The istioctl command line tool has a new bug reporting feature (istioctl bug-report) that can be used to collect debugging information and obtain cluster status.

The way to install add-on has changed. Istioctl is no longer recommended for installation in 1.7 and has been removed directly in 1.8.This helps to solve the problem that add-on lags behind upstream and difficult to maintain.

Mixer has been officially removed. It is recommended to use WebAssembly to extend Istio by extending Envoy. It is also recommended that you use GetEnvoy Toolkit to develop Envoy extensions.

Support for virtual machines

In my previous blog, I talked about how Istio 1.7 supports virtual machines. In Istio 1.8, an intelligent DNS proxy is added, which is an Istio sidecar proxy written by Go. Istio agent on sidecar will come with a cache DNS proxy dynamically programmed by Istiod. DNS queries from applications are transparently intercepted and served by Istio agents in pod or VM. The agent can intelligently respond to DNS query requests and achieve seamless multi-cluster access from virtual machines to service grids.

New WorkloadGroup is added, which describes a collection of workload instances. Provides a specification that workload instances can use to guide their agents, including metadata and identity. It is intended to be used only with non-Kubernetes workloads such as virtual machines and is designed to boot the Istio agent by mimicking the existing sidecar injection and deployment specification model for Kubernetes workloads.

At Tetrate, we widely use this mechanism in customer multi-cluster deployments to enable sidecar to parse DNS and access through mTLS for hosts exposed to ingress gateways of all clusters in the grid.

This is the end of the content of "what functions have been added to Istio 1.8". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.