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

replaced dotted line with dashed line (#1020) 

to distinguish the mesh boundary vs. grouping of multiple services with different versions
This commit is contained in:
Vadim Eisenberg 2018-02-21 18:09:24 +02:00 committed by Martin Taillefer
parent 6f41722c31
commit a7cf7c9bb6
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_blog/2018/egress-https.md
View File

@ -53,7 +53,7 @@ The updated architecture of the application now looks as follows:
caption='The Bookinfo Application with details V2'
%}
Note that the Google Books web service is outside the Istio service mesh, the boundary of which is marked by a dotted line.
Note that the Google Books web service is outside the Istio service mesh, the boundary of which is marked by a dashed line.
Now let's direct all the traffic destined to the _details_ microservice, to _details version v2_, using the following _route rule_:

2
_blog/2018/egress-tcp.md
View File

@ -175,7 +175,7 @@ The updated architecture appears below. Note that the blue arrows inside the mes
caption='The Bookinfo Application with ratings v2-mysql and an external MySQL database'
%}
Note that the MySQL database is outside the Istio service mesh, or more precisely outside the Kubernetes cluster. The boundary of the service mesh is marked by a dotted line.
Note that the MySQL database is outside the Istio service mesh, or more precisely outside the Kubernetes cluster. The boundary of the service mesh is marked by a dashed line.
### Access the webpage
Let's access the webpage of the application, after [determining the ingress IP and port]({{home}}/docs/guides/bookinfo.html#determining-the-ingress-ip-and-port).