Next batch of file refactorings.

content/blog/2017/0.1-using-network-policy/index.md

@@ -104,7 +104,7 @@ spec:
 Here is the service graph for the Bookinfo application.
 
 {{< image width="80%" ratio="59.08%"
-    link="/docs/guides/img/bookinfo/withistio.svg"
+    link="/docs/guides/bookinfo/withistio.svg"
     caption="Bookinfo Service Graph"
     >}}
 

content/blog/2018/egress-https/index.md

@@ -26,7 +26,7 @@ The Bookinfo configuration files reside in the `samples/bookinfo/kube` directory
 Here is a copy of the end-to-end architecture of the application from the original [Bookinfo Guide](/docs/guides/bookinfo/).
 
 {{< image width="80%" ratio="59.08%"
-    link="/docs/guides/img/bookinfo/withistio.svg"
+    link="/docs/guides/bookinfo/withistio.svg"
     caption="The Original Bookinfo Application"
     >}}
 

content/blog/2018/egress-tcp/index.md

@@ -127,7 +127,7 @@ The example commands in this blog post work with Istio 0.3+, with or without [Mu
 As a reminder, here is the end-to-end architecture of the application from the [Bookinfo Guide](/docs/guides/bookinfo/).
 
 {{< image width="80%" ratio="59.08%"
-    link="/docs/guides/img/bookinfo/withistio.svg"
+    link="/docs/guides/bookinfo/withistio.svg"
     caption="The original Bookinfo application"
     >}}
 

content/docs/guides/bookinfo/index.md

@@ -38,7 +38,7 @@ There are 3 versions of the reviews microservice:
 The end-to-end architecture of the application is shown below.
 
 {{< image width="80%" ratio="68.52%"
-    link="../img/bookinfo/noistio.svg"
+    link="./noistio.svg"
     caption="Bookinfo Application without Istio"
     >}}
 
@@ -61,7 +61,7 @@ The needed commands and configuration vary depending on the runtime environment
 although in all cases the resulting deployment will look like this:
 
 {{< image width="80%" ratio="59.08%"
-    link="../img/bookinfo/withistio.svg"
+    link="./withistio.svg"
     caption="Bookinfo Application"
     >}}
 

content/docs/guides/integrating-vms/index.md

@@ -16,7 +16,7 @@ VMs cannot initiate any direct communication to Kubernetes Pods even when using
 ## Overview
 
 {{< image width="80%" ratio="56.78%"
-    link="../img/mesh-expansion.svg"
+    link="./mesh-expansion.svg"
     caption="Bookinfo Application with Istio Mesh Expansion"
     >}}
 

content/docs/setup/kubernetes/quick-start-gke-dm/index.md

@@ -26,14 +26,14 @@ application.  It uses Deployment Manager to automate the steps detailed in the [
 To set this up, navigate to the **IAM** section of the [Cloud Console](https://console.cloud.google.com/iam-admin/iam/project) as shown below and find your default GCE/GKE service account in the following form: `projectNumber-compute@developer.gserviceaccount.com`: by default it should just have the **Editor** role. Then in the **Roles** drop-down list for that account, find the **Kubernetes Engine** group and select the role **Kubernetes Engine Admin**. The **Roles** listing for your account will change to **Multiple**.
 
 {{< image width="100%" ratio="22.94%"
-link="../img/dm_gcp_iam.png"
+link="./dm_gcp_iam.png"
 caption="GKE-IAM Service"
 >}}
 
 Then add the `Kubernetes Engine Admin` role:
 
 {{< image width="70%" ratio="65.04%"
-link="../img/dm_gcp_iam_role.png"
+link="./dm_gcp_iam_role.png"
 caption="GKE-IAM Role"
 >}}
 
@@ -57,7 +57,7 @@ caption="GKE-IAM Role"
 1.  Click **Deploy**:
 
     {{< image width="100%" ratio="67.17%"
-    link="../img/dm_launcher.png"
+    link="./dm_launcher.png"
     caption="GKE-Istio Launcher"
     >}}
 
@@ -131,7 +131,7 @@ Note down the IP address (EXTERNAL-IP) and port assigned to the Bookinfo product
 You can also view the installation using the ***Kubernetes Engine -> Workloads** section on the [Cloud Console](https://console.cloud.google.com/kubernetes/workload):
 
 {{< image width="70%" ratio="80.37%"
-    link="../img/dm_kubernetes_workloads.png"
+    link="./dm_kubernetes_workloads.png"
     caption="GKE-Workloads"
     >}}
 
@@ -148,7 +148,7 @@ You can also view the installation using the ***Kubernetes Engine -> Workloads**
 1.  Verify you can access the Bookinfo ```http://${GATEWAY_URL}/productpage```:
 
     {{< image width="100%" ratio="45.04%"
-    link="../img/dm_bookinfo.png"
+    link="./dm_bookinfo.png"
     caption="Bookinfo"
     >}}
 
@@ -178,7 +178,7 @@ http://localhost:3000/dashboard/db/istio-dashboard
 You should see some statistics for the requests you sent earlier.
 
 {{< image width="100%" ratio="48.49%"
-    link="../img/dm_grafana.png"
+    link="./dm_grafana.png"
     caption="Grafana"
     >}}
 
@@ -199,7 +199,7 @@ http://localhost:9090/graph
 ```
 
 {{< image width="100%" ratio="43.88%"
-    link="../img/dm_prometheus.png"
+    link="./dm_prometheus.png"
     caption="Prometheus"
     >}}
 
@@ -220,7 +220,7 @@ http://localhost:8088/dotviz
 ```
 
 {{< image width="100%" ratio="53.33%"
-    link="../img/dm_servicegraph.png"
+    link="./dm_servicegraph.png"
     caption="ServiceGraph"
     >}}
 
@@ -237,7 +237,7 @@ $ kubectl port-forward -n istio-system $(kubectl get pod -n istio-system -l app=
 You should see the trace statistics sent earlier on [http://localhost:16686](http://localhost:16686)
 
 {{< image width="100%" ratio="42.35%"
-    link="../img/dm-tracing.png"
+    link="./dm-tracing.png"
     caption="Tracing Dashboard"
     >}}
 

content/docs/tasks/telemetry/distributed-tracing/index.md

@@ -42,7 +42,7 @@ With the Bookinfo application up and running, generate trace information by acce
 If you now look at the dashboard, you should see something similar to the following:
 
 {{< image width="100%" ratio="42.35%"
-    link="../img/istio-tracing-list.png"
+    link="./istio-tracing-list.png"
     caption="Tracing Dashboard"
     >}}
 
@@ -51,7 +51,7 @@ latest refresh of the `/productpage`.
 The page should look something like this:
 
 {{< image width="100%" ratio="42.35%"
-    link="../img/istio-tracing-details.png"
+    link="./istio-tracing-details.png"
     caption="Detailed Trace View"
     >}}
 

content/docs/tasks/telemetry/querying-metrics/index.md

@@ -58,7 +58,7 @@ application.
 The results will be similar to:
 
 {{< image width="100%" ratio="39.36%"
-    link="../img/prometheus_query_result.png"
+    link="./prometheus_query_result.png"
     caption="Prometheus Query Result"
     >}}
 

content/docs/tasks/telemetry/servicegraph/index.md

@@ -67,7 +67,7 @@ the example application throughout this task.
     The results will look similar to:
 
     {{< image width="75%" ratio="107.7%"
-    link="../img/servicegraph-example.png"
+    link="./servicegraph-example.png"
     caption="Example Servicegraph"
     >}}
 

content/docs/tasks/telemetry/tcp-metrics/index.md

@@ -207,7 +207,7 @@ These attributes are generated by server-side Envoy proxies. They are forwarded
 protocols within policies.
 
 {{< image width="100%" ratio="192.50%"
-    link="../img/istio-tcp-attribute-flow.svg"
+    link="./istio-tcp-attribute-flow.svg"
     alt="Attribute Generation Flow for TCP Services in an Istio Mesh."
     caption="TCP Attribute Flow"
     >}}

content/docs/tasks/telemetry/using-istio-dashboard/index.md

@@ -51,7 +51,7 @@ the example application throughout this task.
     The Istio Dashboard will look similar to:
 
     {{< image width="100%" ratio="56.57%"
-        link="../img/grafana-istio-dashboard.png"
+        link="./grafana-istio-dashboard.png"
         caption="Istio Dashboard"
         >}}
 
@@ -71,7 +71,7 @@ the example application throughout this task.
     generated. It will look similar to:
 
     {{< image width="100%" ratio="56.57%"
-    link="../img/dashboard-with-traffic.png"
+    link="./dashboard-with-traffic.png"
     caption="Istio Dashboard With Traffic"
     >}}
 

content_zh/docs/concepts/traffic-management/load-balancing.md

@@ -11,12 +11,12 @@ keywords: [traffic-management,load-balancing]
 
 **服务发现**：Pilot 使用来自服务注册的信息，并提供与平台无关的服务发现接口。网格中的 Envoy 实例执行服务发现，并相应地动态更新其负载均衡池。
 
-{{< image width="80%" ratio="74.79%"
+{{</* image width="80%" ratio="74.79%"
     link="../img/pilot/LoadBalancing.svg"
     caption="发现与负载均衡"
-    >}}
+    */>}}
 
-如上图所示，网格中的服务使用其 DNS 名称访问彼此。服务的所有 HTTP 流量都会通过 Envoy 自动重新路由。Envoy 在负载均衡池中的实例之间分发流量。虽然 Envoy 支持多种[复杂的负载均衡算法][https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/load_balancing]，但 Istio 目前仅允许三种负载平衡模式：轮循、随机和带权重的最少请求。
+如上图所示，网格中的服务使用其 DNS 名称访问彼此。服务的所有 HTTP 流量都会通过 Envoy 自动重新路由。Envoy 在负载均衡池中的实例之间分发流量。虽然 Envoy 支持多种[复杂的负载均衡算法](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/load_balancing)，但 Istio 目前仅允许三种负载平衡模式：轮循、随机和带权重的最少请求。
 
 除了负载均衡外，Envoy 还会定期检查池中每个实例的运行状况。Envoy 遵循熔断器风格模式，根据健康检查 API 调用的失败率将实例分类为不健康或健康。换句话说，当给定实例的健康检查失败次数超过预定阈值时，它将从负载均衡池中弹出。类似地，当通过的健康检查数超过预定阈值时，该实例将被添加回负载均衡池。您可以在[处理故障](/docs/concepts/traffic-management/handling-failures/)中了解更多有关 Envoy 的故障处理功能。