You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by ke...@apache.org on 2021/02/21 12:37:54 UTC
[skywalking-website] branch blog/vm-als created (now 83ee4de)
This is an automated email from the ASF dual-hosted git repository.
kezhenxu94 pushed a change to branch blog/vm-als
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git.
at 83ee4de Add blog Observe VM Service Meshes with Apache SkyWalking and the Envoy Access Log Service
This branch includes the following new commits:
new 83ee4de Add blog Observe VM Service Meshes with Apache SkyWalking and the Envoy Access Log Service
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[skywalking-website] 01/01: Add blog Observe VM Service Meshes with
Apache SkyWalking and the Envoy Access Log Service
Posted by ke...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
kezhenxu94 pushed a commit to branch blog/vm-als
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git
commit 83ee4de7ef9835b50626302d62359fed6dcadb43
Author: kezhenxu94 <ke...@apache.org>
AuthorDate: Sun Feb 21 20:37:15 2021 +0800
Add blog Observe VM Service Meshes with Apache SkyWalking and the Envoy Access Log Service
---
.../obs-service-mesh-vm-with-sw-and-als/image1.png | Bin 0 -> 112262 bytes
.../obs-service-mesh-vm-with-sw-and-als/image2.png | Bin 0 -> 132748 bytes
.../obs-service-mesh-vm-with-sw-and-als/image3.png | Bin 0 -> 230538 bytes
.../obs-service-mesh-vm-with-sw-and-als/image4.png | Bin 0 -> 94280 bytes
.../obs-service-mesh-vm-with-sw-and-als/image5.png | Bin 0 -> 180438 bytes
.../obs-service-mesh-vm-with-sw-and-als/image6.png | Bin 0 -> 335111 bytes
.../obs-service-mesh-vm-with-sw-and-als/image7.png | Bin 0 -> 271826 bytes
.../obs-service-mesh-vm-with-sw-and-als/image8.png | Bin 0 -> 228943 bytes
.../obs-service-mesh-vm-with-sw-and-als/image9.png | Bin 0 -> 215018 bytes
.../obs-service-mesh-vm-with-sw-and-als/index.md | 179 +++++++++++++++++++++
.../stone-arch.jpg | Bin 0 -> 119192 bytes
.../Screen-Shot-2020-12-02-at-2.25.17-PM.png | Bin
.../Screen-Shot-2020-12-02-at-2.37.49-PM.png | Bin
.../Screen-Shot-2020-12-02-at-2.43.16-PM.png | Bin
.../Screen-Shot-2020-12-02-at-2.46.56-PM.png | Bin
.../Screen-Shot-2020-12-02-at-3.01.03-PM.png | Bin
.../Screen-Shot-2020-12-02-at-3.05.24-PM.png | Bin
.../Screen-Shot-2020-12-02-at-3.11.55-PM.png | Bin
.../canyonhorseshoe.jpg | Bin
.../index.md | 0
.../index.md | 14 +-
21 files changed, 186 insertions(+), 7 deletions(-)
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image1.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image1.png
new file mode 100644
index 0000000..f33e273
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image1.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image2.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image2.png
new file mode 100644
index 0000000..5502e00
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image2.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image3.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image3.png
new file mode 100644
index 0000000..360dbdc
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image3.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image4.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image4.png
new file mode 100644
index 0000000..bec99cc
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image4.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image5.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image5.png
new file mode 100644
index 0000000..0ae2a2c
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image5.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image6.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image6.png
new file mode 100644
index 0000000..267b4a9
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image6.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image7.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image7.png
new file mode 100644
index 0000000..3a387fd
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image7.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image8.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image8.png
new file mode 100644
index 0000000..6bd48a6
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image8.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/image9.png b/content/blog/obs-service-mesh-vm-with-sw-and-als/image9.png
new file mode 100644
index 0000000..e1aa1c9
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/image9.png differ
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/index.md b/content/blog/obs-service-mesh-vm-with-sw-and-als/index.md
new file mode 100644
index 0000000..31cbaf2
--- /dev/null
+++ b/content/blog/obs-service-mesh-vm-with-sw-and-als/index.md
@@ -0,0 +1,179 @@
+---
+title: "Observe VM Service Meshes with Apache SkyWalking and the Envoy Access Log Service"
+date: 2021-02-21
+author: "[Zhenxu Ke](http://github.com/kezhenxu94) and Hongtao Gao. tetrate.io"
+description: In this tutorial, you can learn how to use Apache SkyWalking for service mesh observability, in Kubernetes and / or in virtual machines.
+tags:
+- Service Mesh
+---
+
+
+
+> Origin: [Observe VM Service Meshes with Apache SkyWalking and the Envoy Access Log Service - The New Stack](https://thenewstack.io/observe-virtual-machine-service-meshes-with-apache-skywalking-and-the-envoy-access-log-service)
+
+[Apache SkyWalking](https://github.com/apache/skywalking): an APM (application performance monitor) system, especially
+designed for microservices, cloud native, and container-based (Docker, Kubernetes, Mesos) architectures.
+
+[Envoy Access Log Service](https://www.envoyproxy.io/docs/envoy/latest/api-v2/service/accesslog/v2/als.proto): Access
+Log Service (ALS) is an Envoy extension that emits detailed access logs of all requests going through Envoy.
+
+## Background
+
+In the [previous post](/blog/obs-service-mesh-with-sw-and-als), we talked about the observability of service mesh under
+Kubernetes environment, and applied it to the bookinfo application in practice. We also mentioned that, in order to map
+the IP addresses into services, SkyWalking needs access to the service metadata from a Kubernetes cluster, which is not
+available for services deployed in virtual machines (VMs). In this post, we will introduce a new analyzer in SkyWalking
+that leverages Envoy’s metadata exchange mechanism to decouple with Kubernetes. The analyzer is designed to work in
+Kubernetes environments, VM environments, and hybrid environments. If there are virtual machines in your service mesh,
+you might want to try out this new analyzer for better observability, which we will demonstrate in this tutorial.
+
+## How it works
+
+The mechanism of how the analyzer works is the same as what we discussed in
+the [previous post](/blog/obs-service-mesh-with-sw-and-als). What makes VMs different from Kubernetes is that, for VM
+services, there are no places where we can fetch the metadata to map the IP addresses into services.
+
+
+
+The basic idea we present in this article is to carry the metadata along with Envoy’s access logs, which is called
+metadata-exchange mechanism in Envoy. When Istio pilot-agent starts an Envoy proxy as a sidecar of a service, it
+collects the metadata of that service from the Kubernetes platform, or a file on the VM where that service is deployed,
+and injects the metadata into the bootstrap configuration of Envoy. Envoy will carry the metadata transparently when
+emitting access logs to the SkyWalking receiver.
+
+
+
+But how does Envoy compose a piece of a complete access log that involves the client side and server side? When a
+request goes out from Envoy, a plugin of istio-proxy named "metadata-exchange" injects the metadata into the http
+headers (with a prefix like `x-envoy-downstream-`), and the metadata is propagated to the server side. The Envoy sidecar
+of the server side receives the request and parses the headers into metadata, and puts the metadata into the access log,
+keyed by `wasm.downstream_peer`. The server side Envoy also puts its own metadata into the access log keyed
+by `wasm.upstream_peer.` Hence the two sides of a single request are completed.
+
+
+
+With the metadata-exchange mechanism, we can use the metadata directly without any extra query.
+
+
+
+## Example
+
+In this tutorial, we will use another demo
+application [Online Boutique](http://github.com/GoogleCloudPlatform/microservices-demo) that consists of 10+ services so
+that we can deploy some of them in VMs and make them communicate with other services deployed in Kubernetes.
+
+
+
+Topology of Online Boutique In order to cover as many cases as possible, we will deploy `CheckoutService`
+and `PaymentService` on VM and all the other services on Kubernetes, so that we can cover the cases like Kubernetes →
+VM (e.g. `Frontend` → `CheckoutService`), VM → Kubernetes (e.g. `CheckoutService` → `ShippingService`), and VM → VM (
+e.g. `CheckoutService` → `PaymentService`).
+
+**NOTE**: All the commands used in this tutorial are accessible
+on [GitHub](https://github.com/SkyAPMTest/sw-als-vm-demo-scripts).
+
+```shell
+git clone https://github.com/SkyAPMTest/sw-als-vm-demo-scripts
+cd sw-als-vm-demo-scripts
+```
+
+Make sure to init the `gcloud` SDK properly before moving on. Modify the `GCP_PROJECT` in file `env.sh` to your own
+project name. Most of the other variables should be OK to work if you keep them intact. If you would like to
+use `ISTIO_VERSION` >/= 1.8.0, please make sure [this patch](https://github.com/istio/istio/pull/28956) is included.
+
+* Prepare Kubernetes cluster and VM instances
+ [`00-create-cluster-and-vms.sh`](https://github.com/SkyAPMTest/sw-als-vm-demo-scripts/blob/2179d04270c98b9f87cf3998f5af775870ed53a7/00-create-cluster-and-vms.sh)
+ creates a new GKE cluster and 2 VM instances that will be used through the entire tutorial, and sets up some necessary
+ firewall rules for them to communicate with each other.
+* Install Istio and SkyWalking
+ [`01a-install-istio.sh`](https://github.com/SkyAPMTest/sw-als-vm-demo-scripts/blob/2179d04270c98b9f87cf3998f5af775870ed53a7/01a-install-istio.sh)
+ installs Istio Operator with spec `resources/vmintegration.yaml`. In the YAML file, we enable the `meshExpansion` that
+ supports VM in mesh. We also enable the Envoy access log service and specify the
+ address `skywalking-oap.istio-system.svc.cluster.local:11800` to which Envoy emits the access logs.
+ [`01b-install-skywalking.sh`](https://github.com/SkyAPMTest/sw-als-vm-demo-scripts/blob/2179d04270c98b9f87cf3998f5af775870ed53a7/01b-install-skywalking.sh)
+ installs Apache SkyWalking and sets the analyzer to `mx-mesh`.
+* Create files to initialize the VM
+ [`02-create-files-to-transfer-to-vm.sh`](https://github.com/SkyAPMTest/sw-als-vm-demo-scripts/blob/2179d04270c98b9f87cf3998f5af775870ed53a7/02-create-files-to-transfer-to-vm.sh)
+ creates necessary files that will be used to initialize the VMs.
+ [`03-copy-work-files-to-vm.sh`](https://github.com/SkyAPMTest/sw-als-vm-demo-scripts/blob/2179d04270c98b9f87cf3998f5af775870ed53a7/03-copy-work-files-to-vm.sh)
+ securely transfers the generated files to the VMs with `gcloud scp` command. Now use `./ssh.sh checkoutservice`
+ and `./ssh.sh paymentservice` to log into the two VMs respectively, and `cd` to the `~/work` directory,
+ execute `./prep-checkoutservice.sh` on `checkoutservice` VM instance and `./prep-paymentservice.sh`
+ on `paymentservice` VM instance. The Istio sidecar should be installed and started properly. To verify that,
+ use `tail -f /var/logs/istio/istio.log` to check the Istio logs. The output should be something like:
+
+ ```
+ 2020-12-12T08:07:07.348329Z info sds resource:default new connection
+ 2020-12-12T08:07:07.348401Z info sds Skipping waiting for gateway secret
+ 2020-12-12T08:07:07.348401Z info sds Skipping waiting for gateway secret
+ 2020-12-12T08:07:07.568676Z info cache Root cert has changed, start rotating root cert for SDS clients
+ 2020-12-12T08:07:07.568718Z info cache GenerateSecret default
+ 2020-12-12T08:07:07.569398Z info sds resource:default pushed key/cert pair to proxy
+ 2020-12-12T08:07:07.949156Z info cache Loaded root cert from certificate ROOTCA
+ 2020-12-12T08:07:07.949348Z info sds resource:ROOTCA pushed root cert to proxy
+ 2020-12-12T20:12:07.384782Z info sds resource:default pushed key/cert pair to proxy
+ 2020-12-12T20:12:07.384832Z info sds Dynamic push for secret default
+ ```
+
+ The dnsmasq configuration `address=/.svc.cluster.local/{ISTIO_SERVICE_IP_STUB}` also resolves the domain names ended
+ with `.svc.cluster.local` to Istio service IP, so that you are able to access the Kubernetes services in the VM by
+ fully qualified domain name (FQDN) such as `httpbin.default.svc.cluster.local`.
+
+* Deploy demo application Because we want to deploy `CheckoutService` and `PaymentService` manually on
+ VM, `resources/google-demo.yaml` removes the two services
+ from [the original YAML](https://github.com/GoogleCloudPlatform/microservices-demo/blob/master/release/kubernetes-manifests.yaml)
+ .
+ [`04a-deploy-demo-app.sh`](https://github.com/SkyAPMTest/sw-als-vm-demo-scripts/blob/2179d04270c98b9f87cf3998f5af775870ed53a7/04a-deploy-demo-app.sh)
+ deploys the other services on Kubernetes. Then log into the 2 VMs, run `~/work/deploy-checkoutservice.sh`
+ and `~/work/deploy-paymentservice.sh` respectively to deploy `CheckoutService` and `PaymentService`.
+
+* Register VMs to Istio Services on VMs can access the services on Kubernetes by FQDN, but that’s not the case when the
+ Kubernetes services want to talk to the VM services. The mesh has no idea where to forward the requests such
+ as `checkoutservice.default.svc.cluster.local` because `checkoutservice` is isolated in the VM. Therefore, we need to
+ register the services to the
+ mesh. [`04b-register-vm-with-istio.sh`](https://github.com/SkyAPMTest/sw-als-vm-demo-scripts/blob/2179d04270c98b9f87cf3998f5af775870ed53a7/04b-register-vm-with-istio.sh)
+ registers the VM services to the mesh by creating a "dummy" service without running Pods, and a `WorkloadEntry` to
+ bridge the "dummy" service with the VM service.
+
+## Done!
+
+The demo application contains a `load generator` service that performs requests repeatedly. We only need to wait a few
+seconds, and then open the SkyWalking web UI to check the results.
+
+```
+export POD_NAME=$(kubectl get pods --namespace istio-system -l "app=skywalking,release=skywalking,component=ui" -o jsonpath="{.items[0].metadata.name}")
+echo "Visit http://127.0.0.1:8080 to use your application"
+kubectl port-forward $POD_NAME 8080:8080 --namespace istio-system
+```
+
+Navigate the browser to http://localhost:8080 . The metrics, topology should be there.
+
+
+
+
+
+
+
+
+
+## Troubleshooting
+
+If you face any trouble when walking through the steps, here are some common problems and possible solutions:
+
+* VM service cannot access Kubernetes services? It’s likely the DNS on the VM doesn’t correctly resolve the fully
+ qualified domain names. Try to verify that with `nslookup istiod.istio-system.svc.cluster.local`. If it doesn’t
+ resolve to the Kubernetes CIDR address, recheck the step in `prep-checkoutservice.sh` and `prep-paymentservice.sh`. If
+ the DNS works correctly, try to verify that Envoy has fetched the upstream clusters from the control plane
+ with `curl http://localhost:15000/clusters`. If it doesn’t contain the target service,
+ recheck `prep-checkoutservice.sh`.
+
+* Services are normal but nothing on SkyWalking WebUI? Check the SkyWalking OAP logs
+ via `kubectl -n istio-system logs -f $(kubectl get pod -A -l "app=skywalking,release=skywalking,component=oap" -o name)`
+ and WebUI logs
+ via `kubectl -n istio-system logs -f $(kubectl get pod -A -l "app=skywalking,release=skywalking,component=ui" -o name)`
+ to see whether there are any error logs . Also, make sure the time zone at the bottom-right of the browser is set
+ to `UTC +0`.
+
+## Additional Resources
+
+- [Observe a Service Mesh with Envoy ALS](/blog/obs-service-mesh-with-sw-and-als).
diff --git a/content/blog/obs-service-mesh-vm-with-sw-and-als/stone-arch.jpg b/content/blog/obs-service-mesh-vm-with-sw-and-als/stone-arch.jpg
new file mode 100644
index 0000000..3e9a0a7
Binary files /dev/null and b/content/blog/obs-service-mesh-vm-with-sw-and-als/stone-arch.jpg differ
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.25.17-PM.png b/content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.25.17-PM.png
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.25.17-PM.png
rename to content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.25.17-PM.png
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.37.49-PM.png b/content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.37.49-PM.png
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.37.49-PM.png
rename to content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.37.49-PM.png
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.43.16-PM.png b/content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.43.16-PM.png
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.43.16-PM.png
rename to content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.43.16-PM.png
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.46.56-PM.png b/content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.46.56-PM.png
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.46.56-PM.png
rename to content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-2.46.56-PM.png
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.01.03-PM.png b/content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.01.03-PM.png
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.01.03-PM.png
rename to content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.01.03-PM.png
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.05.24-PM.png b/content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.05.24-PM.png
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.05.24-PM.png
rename to content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.05.24-PM.png
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.11.55-PM.png b/content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.11.55-PM.png
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.11.55-PM.png
rename to content/blog/obs-service-mesh-with-sw-and-als/Screen-Shot-2020-12-02-at-3.11.55-PM.png
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/canyonhorseshoe.jpg b/content/blog/obs-service-mesh-with-sw-and-als/canyonhorseshoe.jpg
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/canyonhorseshoe.jpg
rename to content/blog/obs-service-mesh-with-sw-and-als/canyonhorseshoe.jpg
diff --git a/content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/index.md b/content/blog/obs-service-mesh-with-sw-and-als/index.md
similarity index 100%
rename from content/blog/2020-12-03-obs-service-mesh-with-sw-and-als/index.md
rename to content/blog/obs-service-mesh-with-sw-and-als/index.md
diff --git a/content/zh/observe-service-mesh-with-skywalking-and-envoy-access-log-service/index.md b/content/zh/observe-service-mesh-with-skywalking-and-envoy-access-log-service/index.md
index ccd0032..1849601 100644
--- a/content/zh/observe-service-mesh-with-skywalking-and-envoy-access-log-service/index.md
+++ b/content/zh/observe-service-mesh-with-skywalking-and-envoy-access-log-service/index.md
@@ -7,7 +7,7 @@ zh_tags:
- Service Mesh
---
-
+
> **如果你正在寻找在 Mixer 方案以外观察服务网格的更优解，本文正符合你的需要。**
@@ -27,7 +27,7 @@ Apache SkyWalking 一直通过 Istio Mixer 的适配器，支持服务网格的
从可观察性的角度来说，Envoy 一般有两种部署模式︰Sidecar 和路由模式。 Envoy 代理可以代表多项服务（见下图之 1），或者当它作为 Sidecar 时，一般是代表接收和发送请求的单项服务（下图之 2 和 3）。
-
+
在两种模式中，ALS 发放的日志都会带有一个节点标记符。该标记符在路由模式时，以 `router~` （或 `ingress~`）开头，而在 Sidecar 代理模式时，则以 `sidecar~` 开头。
@@ -53,7 +53,7 @@ Apache SkyWalking 一直通过 Istio Mixer 的适配器，支持服务网格的
1. **代理传入请求**︰在此情况下，Envoy 会作为服务器端的 Sidecar，以 `inbound|portNumber|portName|Hostname[or]SidecarScopeID` 格式设定 `upstream_cluster`。
- 
+ 
SkyWalking 分析器会检查 `downstream_remote_address` 是否能够找到对应的 Kubernetes 服务。
@@ -70,7 +70,7 @@ Apache SkyWalking 一直通过 Istio Mixer 的适配器，支持服务网格的
### 代理角色
当 Envoy 被部署为前端代理时，它是独立的服务，并不会像 Sidecar 一样，代表任何其他的服务。所以，我们可以建立客户端以及服务器端的指标数据。
-
+
## 演示范例
在本章，我们会使用典型的 bookinfo 应用，来演示 Apache SkyWalking 8.3.0+ （截至 2020 年 11 月 30 日的最新版本）如何与 Envoy ALS 合作，联手观察服务网格。
@@ -198,7 +198,7 @@ kubectl -n istio-system port-forward $POD_NAME 8080:8080
现在到你的浏览器上访问 [http://localhost:8080](http://localhost:8080/)。你应该会看到 SkyWalking 的 Dashboard。 Dashboard 现在应该是空的，但稍后部署应用和生成流量后，它就会被填满。
-
+
### 部署 Bookinfo 应用
@@ -223,8 +223,8 @@ minikube tunnel
这样做，你就成功完成设置了！再查看 SkyWalking 的 WebUI，你应该会看到 bookinfo 应用的拓扑，以及它每一个单独服务的指标数据。
-
-
+
+
### 疑难解答