mirror of https://github.com/istio/istio.io.git
Fix up trademarked symbols with the right casing/spelling.
This commit is contained in:
parent
889e51336c
commit
e15b3039ef
|
@ -12,7 +12,7 @@ type: markdown
|
|||
---
|
||||
|
||||
The Istio model of a service is independent of how it is represented
|
||||
in the underlying platform (Kubernetes, Mesos, CloudFoundry,
|
||||
in the underlying platform (Kubernetes, Mesos, Cloud Foundry,
|
||||
etc.). Platform-specific adapters are responsible for populating the
|
||||
internal model representation with various fields, from the metadata found
|
||||
in the platform.
|
||||
|
|
|
@ -66,7 +66,7 @@ This application is polyglot, i.e., the microservices are written in different l
|
|||
over time instead of deploying all versions simultaneously.
|
||||
|
||||
Notice that the `istioctl kube-inject` command is used to modify the `bookinfo.yaml`
|
||||
file before creating the deployments. This injects Envoy into kubernetes resources
|
||||
file before creating the deployments. This injects Envoy into Kubernetes resources
|
||||
as documented [here]({{site.bareurl}}/docs/reference/istioctl.html#kube-inject).
|
||||
Consequently, all of the microservices are now packaged with an Envoy sidecar
|
||||
that manages incoming and outgoing calls for the service. The updated diagram looks
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
category: Tasks
|
||||
title: Configuring Ingress/Egress with Envoy
|
||||
overview: This task shows you how to setup Envoy as the kubernetes ingress controller and the egress proxy to external services.
|
||||
overview: This task shows you how to setup Envoy as the Kubernetes ingress controller and the egress proxy to external services.
|
||||
|
||||
order: 30
|
||||
|
||||
|
|
Loading…
Reference in New Issue