istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc(concepts): fix indentation (#4647)

This commit is contained in:
Jian Zeng 2019-07-10 23:19:58 +08:00 committed by mergify[bot]
parent 07d53225d3
commit 2625f059ed
1 changed files with 28 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
content/docs/concepts/traffic-management/index.md
View File

@ -252,7 +252,7 @@ metadata:
name: reviews name: reviews
spec: spec:
hosts: hosts:
- reviews - reviews
http: http:
- route: - route:
- destination: - destination:
@ -371,12 +371,12 @@ metadata:
name: my-vtl-svc name: my-vtl-svc
spec: spec:
hosts: hosts:
- "*.my-co.org" - "*.my-co.org"
http: http:
- route: - route:
- destination: - destination:
host: my-svc host: my-svc
subset: v1 subset: v1
{{< /text >}} {{< /text >}}
In the example, under `spec`, In the example, under `spec`,
@ -426,7 +426,7 @@ easily lead to misconfigurations. Therefore we do
[not recommend it for production deployments](/docs/reference/config/networking/v1alpha3/virtual-service/#Destination). [not recommend it for production deployments](/docs/reference/config/networking/v1alpha3/virtual-service/#Destination).
The following example shows a virtual service configuration with fully qualified traffic routes The following example shows a virtual service configuration with fully qualified traffic routes
for two services in the `my-namespace.svc.cluster.local` Kubernetes namespace. for two services in the `my-namespace` Kubernetes namespace.
The configuration relies on the URI prefixes of the two services to distinguish The configuration relies on the URI prefixes of the two services to distinguish
them. them.
@ -437,7 +437,7 @@ metadata:
name: my-namespace name: my-namespace
spec: spec:
hosts: hosts:
- my-namespace.com - my-namespace.com
http: http:
- match: - match:
- uri: - uri:
@ -489,20 +489,20 @@ metadata:
name: my-vtl-svc name: my-vtl-svc
spec: spec:
hosts: hosts:
- "*" - "*"
http: http:
- match: - match:
- headers: - headers:
cookie: cookie:
regex: "^(.*?;)?(user=jason)(;.*)?$" regex: "^(.*?;)?(user=jason)(;.*)?$"
route: route:
- destination: - destination:
host: my-svc host: my-svc
subset: v2 subset: v2
- route: - route:
- destination: - destination:
host: my-svc host: my-svc
subset: v1 subset: v1
{{< /text >}} {{< /text >}}
In the preceding example, there are two routing rules in the `http` section, In the preceding example, there are two routing rules in the `http` section,
@ -612,7 +612,7 @@ metadata:
name: reviews name: reviews
spec: spec:
hosts: hosts:
- reviews - reviews
http: http:
- match: - match:
- headers: - headers:
@ -637,7 +637,7 @@ metadata:
name: productpage name: productpage
spec: spec:
hosts: hosts:
- productpage - productpage
http: http:
- match: - match:
- uri: - uri:
@ -951,7 +951,7 @@ metadata:
name: virtual-svc name: virtual-svc
spec: spec:
hosts: hosts:
- ext-svc - ext-svc
gateways: gateways:
- ext-host-gwy - ext-host-gwy
{{< /text >}} {{< /text >}}
@ -1165,7 +1165,7 @@ metadata:
name: ratings name: ratings
spec: spec:
hosts: hosts:
- ratings - ratings
http: http:
- route: - route:
- destination: - destination:
@ -1194,7 +1194,7 @@ metadata:
name: ratings name: ratings
spec: spec:
hosts: hosts:
- ratings - ratings
http: http:
- route: - route:
- destination: - destination: