Shulou(Shulou.com)06/01 Report--

In view of the changes in Service Mesh istio-v1.6 and what the code structure is, this article introduces the corresponding analysis and solutions in detail, hoping to help more partners who want to solve this problem to find a simpler and easier way.

Change item type 1.6 (.3) 1.5 or previous meaning remove components Citadel, Sidecar Injector, Galley1.5 as the completion of the closing

Strengthen the function of deleting function items and merge them into Istiod

Replacement installation added: istioctl install; replaces manifest apply

Remove the configuration of abandoned Helm charts and istio-pilot

Add feature item virtual machine support (WorkloadEntry)

Preparation independent of K8S? The function of removing the component Envoy proxyMixerMixer has been moved to Envoy proxy and is currently obsolete & unremoved. After 1.7, the added function item Envoy will be completely removed, and the Wasm/WebAssembly function will be removed.

Code directory description

Based on v1.6.3 (2020.06.22)

Bin/: binary generation script, etc.

Common/:

A small amount of compilation processing

Some dependency processing

Common-protos/: a large number of proto files for efficient RPC of internal components (including third-party components)

Docker/:ca certificate & Dockerfile.base, as the name implies

Galley/: does not change, independent components, responsible for configuration management, including

Verify the correctness of the format and content of configuration information

Mask the underlying processing details of the configuration

Provide the configuration to other components for

Install/: installation?

Support for consul/: installation and consul

Gcp/: installation support for Google cloud platform

Istioctl/: standalone components, istio console

Licenses/: all kinds of licenses, quite a lot

Various installation configurations of manifests/:

Mixer/: old components, definitely obsolete, 1.7 will be completely removed

Operator/: is part of istio/istio from 1. 5 onwards.

MeshConfig: used by run-time istio control plane components

Component configuration API: controls K8S configuration, such as resources, automatic scheduling, pod, etc., and addon components

Helm installation related capabilities (isn't Helm replaced by istioctl? What is the meaning of this part? )

Pilot/: independent component, which acts as a resource management segment in istio (? ), which should be part of istiod

Collection of various components of pkg/:

Istio-agent/: is envoy

...

Prow:prow is a project of the Kubernetes testing Special interest Group and is currently part of kubernetes/test-infra. Prow is a CI/CD system based on Kubernetes that executes Job using all kinds of event drivers.

In addition to executing Job, Prow can also automate GitHub by:-policy configuration, permission control, etc.-/ chat-ops commands in the form of label-automatically merging PR

Release/: gets the unstable version of istioCtl and istio

Test tools / configurations for some scenarios after sample/:istio installation

The code and configuration of security/: security mechanism should be mainly in the aspect of authentication

Test/:, as its name implies.

Tools/: aids, some involving iptables processing

This is the answer to the question about the changes in Service Mesh istio-v1.6 and what the code structure is. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

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.