update references for v0.18 (#117)

* update references for v0.18

Signed-off-by: Michael Kalantar <[email protected]>

* update wordlist

Signed-off-by: Michael Kalantar <[email protected]>

---------

Signed-off-by: Michael Kalantar <[email protected]>

Author: kalantar

.github/wordlist.txt

@@ -12,6 +12,7 @@ CLI
 CLIs
 cronjob
 crontab
+ConfigMap
 DCO
 default_encoding
 declaratively

docs/getting-started/first-abn.md

@@ -31,25 +31,23 @@ A sample application using the Iter8 SDK is provided. Deploy both the frontend a
 
     === "node"
         ```shell
-        kubectl create deployment frontend --image=iter8/abn-sample-frontend-node:0.15.0
+        kubectl create deployment frontend --image=iter8/abn-sample-frontend-node:0.17.3
         kubectl expose deployment frontend --name=frontend --port=8090
         ```
-        <!-- kubectl create deployment frontend --image=kalantar/frontend-node:20230717-1552 -->
 
     === "Go"
         ```shell
-        kubectl create deployment frontend --image=iter8/abn-sample-frontend-go:0.15.0
+        kubectl create deployment frontend --image=iter8/abn-sample-frontend-go:0.17.3
         kubectl expose deployment frontend --name=frontend --port=8090
         ```
-        <!-- kubectl create deployment frontend --image=kalantar/frontend-go:20230717-1339 -->
 
     The frontend component is implemented to call `Lookup()` before each call to the backend component. The frontend component uses the returned version number to route the request to the recommended version of the backend component.
 
 === "backend"
     Deploy an initial version of the *backend* component:
 
     ```shell
-    kubectl create deployment backend --image=iter8/abn-sample-backend:0.13-v1
+    kubectl create deployment backend --image=iter8/abn-sample-backend:0.17-v1
     kubectl label deployment backend iter8.tools/watch="true"
 
     kubectl expose deployment backend --name=backend --port=8091
@@ -68,7 +66,7 @@ metadata:
   labels:
     app.kubernetes.io/managed-by: iter8
     iter8.tools/kind: routemap
-    iter8.tools/version: "v0.17"
+    iter8.tools/version: "v0.18"
 immutable: true
 data:
   strSpec: |
@@ -99,15 +97,15 @@ In separate shells, port-forward requests to the frontend component and generate
     kubectl port-forward service/frontend 8090:8090
     ```
     ```shell
-    curl -s https://raw.githubusercontent.com/iter8-tools/docs/v0.15.0/samples/abn-sample/generate_load.sh | sh -s --
+    curl -s https://raw.githubusercontent.com/iter8-tools/docs/v0.17.3/samples/abn-sample/generate_load.sh | sh -s --
     ```
 
 ## Deploy candidate
 
 Deploy the candidate version of the *backend* component, naming it `backend-candidate-1`.
 
 ```shell
-kubectl create deployment backend-candidate-1 --image=iter8/abn-sample-backend:0.13-v2
+kubectl create deployment backend-candidate-1 --image=iter8/abn-sample-backend:0.17-v2
 kubectl label deployment backend-candidate-1 iter8.tools/watch="true"
 
 kubectl expose deployment backend-candidate-1 --name=backend-candidate-1 --port=8091
@@ -131,7 +129,7 @@ Open Grafana in a browser by going to [http://localhost:3000](http://localhost:3
 * URL: `http://iter8.default:8080/abnDashboard`
 * Query string: `namespace=default&application=backend`
 
-[Create a new dashboard](http://localhost:3000/dashboards) by *import*. Copy and paste the contents of the [`abn` Grafana dashboard](https://raw.githubusercontent.com/iter8-tools/iter8/v0.16.2/grafana/abn.json) into the text box and *load* it. Associate it with the JSON API data source above.
+[Create a new dashboard](http://localhost:3000/dashboards) by *import*. Copy and paste the contents of the [`abn` Grafana dashboard](https://raw.githubusercontent.com/iter8-tools/iter8/v0.18.3/grafana/abn.json) into the text box and *load* it. Associate it with the JSON API data source above.
 
 The Iter8 dashboard allows you to compare the behavior of the two versions of the backend component against each other and select a winner. Since user requests are being sent by the load generation script, the values in the report may change over time. The Iter8 dashboard will look like the following:
 
@@ -144,7 +142,7 @@ Once you identify a winner, it can be promoted, and the candidate version delete
 To promote the candidate version (`backend-candidate-1`), first update the primary version, `backend`, using the new image. You can also overwrite any metadata describing the version.
 
 ```shell
-kubectl set image deployment/backend abn-sample-backend=iter8/abn-sample-backend:0.13-v2
+kubectl set image deployment/backend abn-sample-backend=iter8/abn-sample-backend:0.17-v2
 ```
 
 Finally, delete the candidate version:

docs/getting-started/first-performance.md

@@ -4,7 +4,7 @@ template: main.html
 
 # Load test HTTP endpoint
 
-Run your first [Iter8 performance test](concepts.md#design) by load testing a Kubernetes HTTP service and visualizing the performance with an Iter8 Grafana dashboard.
+Run your first performance test by load testing a Kubernetes HTTP service and visualizing the performance with an Iter8 Grafana dashboard.
 
 ![Load test HTTP](images/kubernetesusage.png)
 
@@ -32,7 +32,7 @@ Run your first [Iter8 performance test](concepts.md#design) by load testing a Ku
 === "GET example"
     ```shell
     helm upgrade --install \
-    --repo https://iter8-tools.github.io/iter8 --version 0.17 httpbin-test iter8 \
+    --repo https://iter8-tools.github.io/iter8 --version 0.18 httpbin-test iter8 \
     --set "tasks={ready,http}" \
     --set ready.deploy=httpbin \
     --set ready.service=httpbin \
@@ -43,7 +43,7 @@ Run your first [Iter8 performance test](concepts.md#design) by load testing a Ku
 === "POST example"
     ```shell
     helm upgrade --install \
-    --repo https://iter8-tools.github.io/iter8 --version 0.17 httpbin-test iter8 \
+    --repo https://iter8-tools.github.io/iter8 --version 0.18 httpbin-test iter8 \
     --set "tasks={ready,http}" \
     --set ready.deploy=httpbin \
     --set ready.service=httpbin \
@@ -73,7 +73,7 @@ Open Grafana by going to [http://localhost:3000](http://localhost:3000).
 * URL: `http://iter8.default:8080/httpDashboard` 
 * Query string: `namespace=default&test=httpbin-test`
 
-[Create a new dashboard](http://localhost:3000/dashboards) by *import*. Paste the contents of the [`http` Grafana dashboard](https://raw.githubusercontent.com/iter8-tools/iter8/v0.16.2/grafana/http.json) into the text box and *load* it. Associate it with the JSON API data source defined above.
+[Create a new dashboard](http://localhost:3000/dashboards) by *import*. Paste the contents of the [`http` Grafana dashboard](https://raw.githubusercontent.com/iter8-tools/iter8/v0.18.3/grafana/http.json) into the text box and *load* it. Associate it with the JSON API data source defined above.
 
 The Iter8 dashboard will look like the following:
 

docs/getting-started/first-routing.md

@@ -49,15 +49,15 @@ kubectl get deployment httpbin-0
 Initialize the routing resources for the application to use a blue-green rollout strategy:
 
 ```shell
-cat <<EOF | helm template routing --repo https://iter8-tools.github.io/iter8 routing-actions --version 0.1.5 -f - | kubectl apply -f -
+cat <<EOF | helm template routing --repo https://iter8-tools.github.io/iter8 routing-actions --version 0.18 -f - | kubectl apply -f -
 appType: deployment
 appName: httpbin
 action: initialize
 strategy: blue-green
 EOF
 ```
 
-The `initialize` action (with strategy `blue-green`) configures the (Istio) service mesh to route all requests to the primary version of the application (`httpbin-0`). It further defines the routing policy that will be used when changes are observed in the application resources. By default, this routing policy splits requests 50-50 between the primary and candidate versions. For detailed configuration options, see the [Helm chart](https://github.com/iter8-tools/iter8/blob/v0.16.0/charts/routing-actions/values.yaml).
+The `initialize` action (with strategy `blue-green`) configures the (Istio) service mesh to route all requests to the primary version of the application (`httpbin-0`). It further defines the routing policy that will be used when changes are observed in the application resources. By default, this routing policy splits requests 50-50 between the primary and candidate versions. For detailed configuration options, see the [Helm chart](https://github.com/iter8-tools/iter8/blob/v0.18.3/charts/routing-actions/values.yaml).
 
 ### Verify routing
 
@@ -72,7 +72,7 @@ To send inference requests to the model:
 === "From within the cluster"
     1. Create a `sleep` pod in the cluster from which requests can be made:
     ```shell
-    curl -s https://raw.githubusercontent.com/iter8-tools/docs/v0.15.2/samples/kserve-serving/sleep.sh | sh -
+    curl -s https://raw.githubusercontent.com/iter8-tools/docs/v0.17.3/samples/kserve-serving/sleep.sh | sh -
     ```
 
     2. Exec into the sleep pod:
@@ -156,7 +156,7 @@ You can send additional inference requests as described above. They will be hand
 You can modify the weight distribution of inference requests as follows:
 
 ```shell
-cat <<EOF | helm template routing --repo https://iter8-tools.github.io/iter8 routing-actions --version 0.1.5 -f - | kubectl apply -f -
+cat <<EOF | helm template routing --repo https://iter8-tools.github.io/iter8 routing-actions --version 0.18 -f - | kubectl apply -f -
 appType: deployment
 appName: httpbin
 action: modify-weights
@@ -208,7 +208,7 @@ kubectl delete deployment/httpbin-1 service/httpbin-1
 Delete routing:
 
 ```shell
-cat <<EOF | helm template routing --repo https://iter8-tools.github.io/iter8 routing-actions --version 0.1.5 -f - | kubectl delete -f -
+cat <<EOF | helm template routing --repo https://iter8-tools.github.io/iter8 routing-actions --version 0.18 -f - | kubectl delete -f -
 appType: deployment
 appName: httpbin
 action: initialize

docs/images/logo.svg

@@ -6,10 +6,10 @@
 === "Kustomize"
     === "Namespace scoped"
         ```shell
-        kubectl delete -k 'https://github.com/iter8-tools/iter8.git/kustomize/controller/namespaceScoped?ref=v0.17.1'
+        kubectl delete -k 'https://github.com/iter8-tools/iter8.git/kustomize/controller/namespaceScoped?ref=v0.18.3'
         ```
 
     === "Cluster scoped"
         ```shell
-        kubectl delete -k 'https://github.com/iter8-tools/iter8.git/kustomize/controller/clusterScoped?ref=v0.17.1'
+        kubectl delete -k 'https://github.com/iter8-tools/iter8.git/kustomize/controller/clusterScoped?ref=v0.18.3'
         ```

docs/tutorials/deleteiter8controller.md

@@ -1,22 +1,22 @@
 === "Helm"
     === "Namespace scoped"
         ```shell
-        helm install --repo https://iter8-tools.github.io/iter8 --version 0.1.12 iter8 controller
+        helm install --repo https://iter8-tools.github.io/iter8 --version 0.18 iter8 controller
         ```
 
     === "Cluster scoped"
         ```shell
-        helm install --repo https://iter8-tools.github.io/iter8 --version 0.1.12 iter8 controller \
+        helm install --repo https://iter8-tools.github.io/iter8 --version 0.18 iter8 controller \
         --set clusterScoped=true
         ```
 
 === "Kustomize"
     === "Namespace scoped"
         ```shell
-        kubectl apply -k 'https://github.com/iter8-tools/iter8.git/kustomize/controller/namespaceScoped?ref=v0.17.1'
+        kubectl apply -k 'https://github.com/iter8-tools/iter8.git/kustomize/controller/namespaceScoped?ref=v0.18.3'
         ```
 
     === "Cluster scoped"
         ```shell
-        kubectl apply -k 'https://github.com/iter8-tools/iter8.git/kustomize/controller/clusterScoped?ref=v0.17.1'
+        kubectl apply -k 'https://github.com/iter8-tools/iter8.git/kustomize/controller/clusterScoped?ref=v0.18.3'
         ```

docs/tutorials/installiter8controller.md

@@ -31,9 +31,9 @@ jobs:
       - run: 'echo "payload: ${{ toJson(github.event.client_payload) }}"'
 ```
 
-Note that this workflow has one job that will print out the `client_payload`. The default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v0.16.5/templates/notify/_payload-github.tpl) is configured with `client_payload` set to `.Report`, a summary of the performance test.
+Note that this workflow has one job that will print out the `client_payload`. The default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v0.18.3/templates/notify/_payload-github.tpl) is configured with `client_payload` set to `.Report`, a summary of the performance test.
 
-Also note that the `on.repository_dispatch.types` is set to `iter8`. The default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v0.16.5/templates/notify/_payload-github.tpl) is configured with `event_type` set to `iter8`. This indicates that once the `repository_dispatch` has been sent, only workflows on the default branch with `on.repository_dispatch.types` set to `iter8` will be triggered.
+Also note that the `on.repository_dispatch.types` is set to `iter8`. The default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v0.18.3/templates/notify/_payload-github.tpl) is configured with `event_type` set to `iter8`. This indicates that once the `repository_dispatch` has been sent, only workflows on the default branch with `on.repository_dispatch.types` set to `iter8` will be triggered.
 
 3. Create a GitHub [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) for the `token` parameter.
 4. Ensure that you have a Kubernetes cluster and the [`kubectl` CLI](https://kubernetes.io/docs/reference/kubectl/). You can create a local Kubernetes cluster using tools like [Kind](https://kind.sigs.k8s.io/) or [Minikube](https://minikube.sigs.k8s.io/docs/).
@@ -49,7 +49,7 @@ kubectl expose deploy httpbin --port=80
 7. Launch the performance test using the `github` task with the appropriate values.
 ```shell
 helm upgrade --install \
---repo https://iter8-tools.github.io/iter8 --version 0.17 httpbin-test iter8 \
+--repo https://iter8-tools.github.io/iter8 --version 0.18 httpbin-test iter8 \
 --set "tasks={http,github}" \
 --set http.url=http://httpbin.default/get \
 --set github.owner=<GitHub owner> \
@@ -59,8 +59,8 @@ helm upgrade --install \
 8. Verify that the workflow has been triggered after the performance test has completed.
 
 ??? note "Some variations and extensions of the `github` task"
-    The default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v0.16.5/templates/notify/_payload-github.tpl) sends a summary of the performance test. 
+    The default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v0.18.3/templates/notify/_payload-github.tpl) sends a summary of the performance test. 
 
     In your workflow, you can read from the report and use that data for control flow or use snippets of that data in different actions. For example, you can check to see if there have been any task failures and take alternative actions.
 
-    You do not need to use the default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v0.16.5/templates/notify/_payload-github.tpl). You can provide your own payload by overriding the default of the `payloadTemplateURL`.
+    You do not need to use the default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v0.18.3/templates/notify/_payload-github.tpl). You can provide your own payload by overriding the default of the `payloadTemplateURL`.

docs/tutorials/integrations/ghactions.md

@@ -32,7 +32,7 @@ A sample application using the Iter8 SDK is provided. Deploy both the frontend a
 
 === "frontend"
     ```shell
-    kubectl create deployment frontend --image=iter8/abn-sample-mm-frontend-go:0.17.2
+    kubectl create deployment frontend --image=iter8/abn-sample-mm-frontend-go:0.17.3
     kubectl expose deployment frontend --name=frontend --port=8090
     ```
 
@@ -83,7 +83,7 @@ metadata:
   labels:
     app.kubernetes.io/managed-by: iter8
     iter8.tools/kind: routemap
-    iter8.tools/version: "v0.17"
+    iter8.tools/version: "v0.18"
 immutable: true
 data:
   strSpec: |
@@ -109,7 +109,7 @@ In separate shells, port-forward requests to the frontend component and generate
     ```
 
     ```shell
-    curl -s https://raw.githubusercontent.com/iter8-tools/docs/v0.15.0/samples/abn-sample/generate_load.sh | sh -s --
+    curl -s https://raw.githubusercontent.com/iter8-tools/docs/v0.17.3/samples/abn-sample/generate_load.sh | sh -s --
     ```
 
 ## Deploy candidate
@@ -159,7 +159,7 @@ Open Grafana in a browser by going to [http://localhost:3000](http://localhost:3
 * URL: `http://iter8.modelmesh-serving:8080/abnDashboard`
 * Query string: `namespace=modelmesh-serving&application=backend`
 
-[Create a new dashboard](http://localhost:3000/dashboards) by *import*. Copy and paste the contents of the [`abn` Grafana dashboard](https://raw.githubusercontent.com/iter8-tools/iter8/v0.16.2/grafana/abn.json) into the text box and *load* it. Associate it with the JSON API data source above.
+[Create a new dashboard](http://localhost:3000/dashboards) by *import*. Copy and paste the contents of the [`abn` Grafana dashboard](https://raw.githubusercontent.com/iter8-tools/iter8/v0.18.3/grafana/abn.json) into the text box and *load* it. Associate it with the JSON API data source above.
 
 The Iter8 dashboard allows you to compare the behavior of the two versions of the backend component against each other and select a winner. Since user requests are being sent by the load generation script, the values in the report may change over time. The Iter8 dashboard will look like the following: