From 1a1d9673849d5ec24d43f59929c900540766ad6b Mon Sep 17 00:00:00 2001 From: LisaFC Date: Tue, 13 Jun 2017 14:27:39 -0700 Subject: [PATCH] Add notes explaining when to use replace rather than create for routing rules (#373) ...if rules already exist * Add note about using "replace" rather than "create" * Implementing Frank's edits * Implementing Frank's edits * Implementing Frank's edits * Implementing Frank's edits --- _docs/tasks/fault-injection.md | 5 ++++- _docs/tasks/request-routing.md | 4 +++- _docs/tasks/request-timeouts.md | 2 ++ 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/_docs/tasks/fault-injection.md b/_docs/tasks/fault-injection.md index a62a644218..ab40a43a3b 100644 --- a/_docs/tasks/fault-injection.md +++ b/_docs/tasks/fault-injection.md @@ -21,12 +21,15 @@ This task shows how to inject delays and test the resiliency of your application * Initialize the application version routing by either first doing the [request routing](./request-routing.html) task or by running following commands: + + > Note: This assumes you don't have any routes set yet. If you've already created conflicting route rules for the sample, you'll need to use `replace` rather than `create` in one or both of the following commands. + ```bash istioctl create -f samples/apps/bookinfo/route-rule-all-v1.yaml istioctl create -f samples/apps/bookinfo/route-rule-reviews-test-v2.yaml ``` - + ## Fault injection To test our BookInfo application microservices for resiliency, we will _inject a 7s delay_ diff --git a/_docs/tasks/request-routing.md b/_docs/tasks/request-routing.md index 3e522c930c..fb05a0cef5 100644 --- a/_docs/tasks/request-routing.md +++ b/_docs/tasks/request-routing.md @@ -22,11 +22,13 @@ This task shows you how to configure dynamic request routing based on weights an Because the BookInfo sample deploys 3 versions of the reviews microservice, we need to set a default route. -Otherwise if you access the application several times, you would notice that sometimes the output contains +Otherwise if you access the application several times, you'll notice that sometimes the output contains star ratings. This is because without an explicit default version set, Istio will route requests to all available versions of a service in a random fashion. +> Note: This task assumes you don't have any routes set yet. If you've already created conflicting route rules for the sample, you'll need to use `replace` rather than `create` in one or both of the following commands. + 1. Set the default version for all microservices to v1. ```bash diff --git a/_docs/tasks/request-timeouts.md b/_docs/tasks/request-timeouts.md index ba7b01ab1b..c7eae70a8e 100644 --- a/_docs/tasks/request-timeouts.md +++ b/_docs/tasks/request-timeouts.md @@ -20,6 +20,8 @@ This task shows you how to setup request timeouts in Envoy using Istio. * Deploy the [BookInfo]({{home}}/docs/samples/bookinfo.html) sample application. * Initialize the application version routing by running the following command: + +> Note: This assumes you don't have any routes set yet. If you've already created route rules for the sample, you'll need to use `replace` rather than `create` in the following command. ```bash istioctl create -f samples/apps/bookinfo/route-rule-all-v1.yaml