Mention kube service restrictions for routing (#1608)

This commit is contained in:
Frank Budinsky 2018-06-27 13:40:46 -04:00 committed by Martin Taillefer
parent 4bf79f2686
commit 051dd01f32
1 changed files with 5 additions and 0 deletions

View File

@ -170,6 +170,11 @@ In this task, you used Istio to send 100% of the traffic to the v1 version of ea
services. You then set a rule to selectively send traffic to version v2 of the reviews service based
on a header (i.e., a user cookie) in a request.
Note that Kubernetes services, like the Bookinfo ones used in this task, must adhere to certain
restrictions in order to take advantage of Istio's L7 routing features. Refer to the
[sidecar injection documentation](/docs/setup/kubernetes/sidecar-injection/#pod-spec-requirements)
for details.
Once the v2 version has been tested to our satisfaction, we could use Istio to send traffic from
all users to v2, optionally in a gradual fashion. We'll explore this in a separate task.