update to 1.1 (#136)

* update to 1.1.1

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

* add to wordlist

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

* add to wordlist

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

* typo; paths

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

---------

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

Author: kalantar

.github/wordlist.txt

@@ -5,6 +5,7 @@ apis
 ArgoCD
 AutoX
 backend
+backends
 BadgerDB
 benchmarking
 Cha
@@ -70,6 +71,7 @@ png
 PRs
 protobuf
 protoc
+provisioner
 quickstart
 roadmap
 routemap
@@ -199,4 +201,4 @@ serviceSpecification
 deploymentSpecification
 kennethreitz
 natively
-finalizers
+finalizers

CONTRIBUTING.md

@@ -115,7 +115,7 @@ docker push $IMG
 
 To install a development build of the controller, set the `image` property to the name of the Docker image $IMG:
 
-```helm upgrade --install --repo https://iter8-tools.github.io/iter8 --version 0.18 contoller \
+```helm upgrade --install --repo https://iter8-tools.github.io/iter8 --version 1.1 contoller \
 --set image=$IMG```
 
 ### iter8-tools/docs

docs/getting-started/first-abn.md

@@ -47,7 +47,7 @@ A simple sample two-tier application using the Iter8 SDK is provided. Note that
     Release an initial version of the backend named `backend`:
 
     ```shell
-    cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+    cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
     environment: deployment
     application: 
       port: 8091
@@ -80,7 +80,7 @@ Recommendation: {"Id":19,"Name":"sample","Source":"backend-74ff88c76d-nb87j"}
 A candidate version of the *backend* component can be deployed simply by adding a second version to the list of versions:
 
 ```shell
-cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment
 application: 
   port: 8091
@@ -118,7 +118,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.18.3/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/v1.1.1/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:
 
@@ -131,7 +131,7 @@ Once you identify a winner, it can be promoted, and the candidate version delete
 To promote the candidate version (`backend-candidate-1`), re-release the application, updating the image of the primary (the first) version to use the image of the candidate version and remove the candidate version:
 
 ```shell
-cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment
 application: 
   port: 8091

docs/getting-started/first-performance.md

@@ -32,7 +32,7 @@ Run your first performance test by load testing a Kubernetes HTTP service and vi
 === "GET example"
     ```shell
     helm upgrade --install \
-    --repo https://iter8-tools.github.io/iter8 --version 0.18 httpbin-test iter8 \
+    --repo https://iter8-tools.github.io/iter8 --version 1.1 httpbin-test iter8 \
     --set "tasks={ready,http}" \
     --set ready.deploy=httpbin \
     --set ready.service=httpbin \
@@ -43,7 +43,7 @@ Run your first performance test by load testing a Kubernetes HTTP service and vi
 === "POST example"
     ```shell
     helm upgrade --install \
-    --repo https://iter8-tools.github.io/iter8 --version 0.18 httpbin-test iter8 \
+    --repo https://iter8-tools.github.io/iter8 --version 1.1 httpbin-test iter8 \
     --set "tasks={ready,http}" \
     --set ready.deploy=httpbin \
     --set ready.service=httpbin \
@@ -73,7 +73,7 @@ Open Grafana in a browser by going to [http://localhost:3000](http://localhost:3
 * 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.18.3/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/v1.1.1/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-release.md

@@ -29,7 +29,7 @@ The chart provides the configuration needed for Iter8 to automatically deploy ap
 Deploy the initial version of the application using the Iter8 `release` chart by identifying the environment into which it should be deployed, a list of the versions to be deployed (only one here), and the release strategy to be used:
 
 ```shell
-cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment-istio
 application: 
   versions:
@@ -100,7 +100,7 @@ app-version: httpbin-0
 A candidate can deployed by simply adding a second version to the list of versions comprising the application:
 
 ```shell
-cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment-istio
 application: 
   versions:
@@ -138,7 +138,7 @@ app-version: httpbin-1
 To modify the request distribution between the versions, add a `weight` to each version. The weights are relative to each other.
 
 ```shell
-cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment-istio
 application: 
   versions:
@@ -167,7 +167,7 @@ You can verify the routing configuration by inspecting the `VirtualService` and/
 The candidate can be promoted by redefining the primary version and removing the candidate:
 
 ```shell
-cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment-istio
 application: 
   versions:

docs/getting-started/install.md

@@ -2,13 +2,13 @@ Iter8 can be installed and configured to watch resources either in a single name
 
 === "Namespace-scoped"
     ```shell
-    helm install --repo https://iter8-tools.github.io/iter8 --version 0.18 iter8 controller
+    helm install --repo https://iter8-tools.github.io/iter8 --version 1.1 iter8 controller
     ```
 
 === "Cluster-scoped"
     ```shell
-    helm install --repo https://iter8-tools.github.io/iter8 --version 0.18 iter8 controller \
+    helm install --repo https://iter8-tools.github.io/iter8 --version 1.1 iter8 controller \
     --set clusterScoped=true
     ```
 
-For additional install options, see [Iter8 Installation](https://iter8.tools/0.18/user-guide/install/).
+For additional install options, see [Iter8 Installation](https://iter8.tools/1.1.0/user-guide/install/).

docs/getting-started/uninstall.md

@@ -2,4 +2,4 @@
 helm delete iter8
 ```
 
-For additional uninstall options, see [Iter8 Uninstall](https://iter8.tools/0.18/user-guide/uninstall/).
+For additional uninstall options, see [Iter8 Uninstall](https://iter8.tools/1.1.0/user-guide/uninstall/).

docs/tutorials/canary.md

@@ -28,7 +28,7 @@ The chart provides the configuration needed for Iter8 to automatically deploy ap
 Deploy the initial version of the application using the Iter8 `release` chart by identifying the environment into which it should be deployed, a list of the versions to be deployed (only one here), and the release strategy to be used:
 
 ```shell
-cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment-istio
 application: 
   versions:
@@ -99,7 +99,7 @@ app-version: httpbin-0
 A candidate can deployed by simply adding a second version to the list of versions comprising the application:
 
 ```shell
-cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment-istio
 application: 
   versions:
@@ -141,7 +141,7 @@ You can verify the routing configuration by inspecting the `VirtualService` and/
 The candidate can be promoted by redefining the primary version and removing the candidate:
 
 ```shell
-cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install httpbin --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: deployment-istio
 application: 
   versions:

docs/tutorials/integrations/ghactions.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.18.3/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/v1.1.1/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.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.
+Also note that the `on.repository_dispatch.types` is set to `iter8`. The default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v1.1.1/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.18 httpbin-test iter8 \
+--repo https://iter8-tools.github.io/iter8 --version 1.1 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.18.3/templates/notify/_payload-github.tpl) sends a summary of the performance test. 
+    The default `github` task [payload](https://raw.githubusercontent.com/iter8-tools/iter8/v1.1.1/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.18.3/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/v1.1.1/templates/notify/_payload-github.tpl). You can provide your own payload by overriding the default of the `payloadTemplateURL`.

docs/tutorials/integrations/kserve-mm/abn.md

@@ -41,7 +41,7 @@ kubectl expose deployment frontend --name=frontend --port=8090
 The backend application component is an ML model. Release it using the Iter8 `release` chart:
 
 ```shell
-cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: kserve-modelmesh-istio
 application: 
   metadata:
@@ -87,7 +87,7 @@ Recommendation: backend-0__isvc-3642375d03
 A candidate version of the model can be deployed simply by adding a second version to the list of versions:
 
 ```shell
-cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: kserve-modelmesh-istio
 application: 
   metadata:
@@ -135,7 +135,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.18.3/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/v1.1.1/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:
 
@@ -148,7 +148,7 @@ Once you identify a winner, it can be promoted, and the candidate version delete
 The candidate can be promoted by redefining the primary version and removing the candidate:
 
 ```shell
-cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 0.18 -f -
+cat <<EOF | helm upgrade --install backend --repo https://iter8-tools.github.io/iter8 release --version 1.1 -f -
 environment: kserve-modelmesh-istio
 application: 
   metadata: