Make sure all file references point to the correct branch

Author: fabolive

doc_files/iter8_bookinfo_istio.md

@@ -14,7 +14,7 @@ The tutorial is based on the [Bookinfo sample application](https://istio.io/docs
 
 ## YAML files used in the tutorial
 
-All Kubernetes YAML files you will need in this tutorial are in the _iter8-controller_ repository [here](https://github.com/iter8-tools/iter8-controller/tree/master/doc/tutorials/istio/bookinfo). 
+All Kubernetes YAML files you will need in this tutorial are in the _iter8-controller_ repository [here](https://github.com/iter8-tools/iter8-controller/tree/v0.1.0/doc/tutorials/istio/bookinfo). 
 
 ## Part 1: Successful canary release: _reviews-v2_ to _reviews-v3_
 
@@ -25,13 +25,13 @@ At this point, we assume that you have already followed the [instructions](iter8
 First, let us create a `bookinfo-iter8` namespace configured to enable auto-injection of the Istio sidecar:
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/namespace.yaml
+kubectl apply -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/namespace.yaml
 ```
 
 Next, let us deploy the Bookinfo application:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/bookinfo-tutorial.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/bookinfo-tutorial.yaml
 ```
 
 You should see the following pods in the `bookinfo-iter8` namespace. Make sure the pods' status is "Running." Also, note that there should be 2 containers in each pod, since the Istio sidecar was injected.
@@ -50,7 +50,7 @@ We have deployed "version 2" of the _reviews_ microservice, and version 1 of all
 Let us now expose the edge _productpage_ service by creating an Istio Gateway for it.
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/bookinfo-gateway.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/bookinfo-gateway.yaml
 ```
 
 You should now see the Istio Gateway and VirtualService for _productpage_, as below:
@@ -136,7 +136,7 @@ In the example above, we specified only one success criterion. In particular, we
 The next step of this tutorial is to actually create the configuration above. To that end, you can either copy and paste the yaml above to a file and then run `kubectl apply -n bookinfo-iter8 -f` on it, or you can run the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/canary_reviews-v2_to_reviews-v3.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/canary_reviews-v2_to_reviews-v3.yaml
 ```
 
 You can verify that the `Experiment` object has been created as shown below:
@@ -154,7 +154,7 @@ As you can see, _iter8_ is reporting that 100% of the traffic is sent to the bas
 As soon as we deploy _reviews-v3_, _iter8-controller_ will start the rollout. To deploy _reviews-v3_, you can run the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/reviews-v3.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/reviews-v3.yaml
 ```
 
 Now, if you check the state of the `Experiment` object corresponding to this rollout, you should see that the rollout is in progress, and that 20% of the traffic is now being sent to _reviews-v3_:
@@ -234,7 +234,7 @@ The configuration above is pretty much the same we used in part 1, except that n
 To create the above `Experiment` object, run the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/canary_reviews-v3_to_reviews-v4.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/canary_reviews-v3_to_reviews-v4.yaml
 ```
 
 You can list all `Experiment` objects like so:
@@ -255,7 +255,7 @@ As you have already seen, as soon as we deploy the candidate version, _iter8-con
 To deploy _reviews-v4_, run the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/reviews-v4.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/reviews-v4.yaml
 ```
 
 Now, if you check the state of the `Experiment` object corresponding to this rollout, you should see that the rollout is in progress, and that 20% of the traffic is now being sent to _reviews-v4_.
@@ -341,7 +341,7 @@ The configuration above differs from the previous ones as follows. We added a se
 To create the above `Experiment` object, run the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/canary_reviews-v3_to_reviews-v5.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/canary_reviews-v3_to_reviews-v5.yaml
 ```
 
 ### 2. Deploy _reviews-v5_ and start the rollout
@@ -351,7 +351,7 @@ As you already know, as soon as we deploy the candidate version, _iter8-controll
 To deploy _reviews-v5_, run the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/reviews-v5.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/reviews-v5.yaml
 ```
 
 If you check the state of the `Experiment` object corresponding to this rollout, you should see that the rollout is in progress, and that 20% of the traffic is now being sent to _reviews-v5_.
@@ -412,7 +412,7 @@ $ kubectl get configmap iter8config-metrics -n iter8 -oyaml
 In principle, any metric that can be derived from the data you have in your Prometheus database that might be meaningful to you in assessing the health of a service version can be used by _iter8_. Next, we are going to make _iter8_ aware of a metric that we will call _iter8_90_perc_latency_, which measures the 90th percentile latency of a service. In order to make _iter8_ aware of a new metric we need to add it to the _iter8config-metrics_ config map. For the purposes of this tutorial, we will do so by running the following command:
 
 ```bash
-$ kubectl apply -n iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/iter8_metrics_extended.yaml
+$ kubectl apply -n iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/iter8_metrics_extended.yaml
 ```
 
 #### Note:
@@ -461,7 +461,7 @@ The configuration uses the newly extended metric _iter8_90_perc_latency_. The su
 To create the above `Experiment` object, run the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/canary_reviews-v3_to_reviews-v6.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/canary_reviews-v3_to_reviews-v6.yaml
 ```
 
 As usual, iter8 is waiting for the candidate version to be deployed:
@@ -482,7 +482,7 @@ As soon as we deploy the candidate version, _iter8-controller_ will start the ro
 To deploy _reviews-v6_, run the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/reviews-v6.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/reviews-v6.yaml
 ```
 
 If you check the state of the `Experiment` object corresponding to this rollout, you should see that the rollout is in progress, and that 20% of the traffic is now being sent to _reviews-v6_.
@@ -624,7 +624,7 @@ If you look carefully at the definition above, you will notice a reference to th
 Let us now create the `Experiment` object above by running the following command:
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/canary_productpage-v1_to_productpage-v2.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/canary_productpage-v1_to_productpage-v2.yaml
 ```
 
 You can verify that the `Experiment` object has been created:
@@ -640,7 +640,7 @@ productpage-v2-rollout   Pause   TargetsNotFound: Missing Candidate   productpag
 To start the rollout let us deploy the candidate version (_productpage-v2_).
 
 ```bash
-kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/master/doc/tutorials/istio/bookinfo/productpage-v2.yaml
+kubectl apply -n bookinfo-iter8 -f https://raw.githubusercontent.com/iter8-tools/iter8-controller/v0.1.0/doc/tutorials/istio/bookinfo/productpage-v2.yaml
 ```
 
 You can verify that experiment has started: