Deployment patterns (#675)

* Progressive tutorial with no-code

* Fixed split figures

* fixed split deployment

* Updated doc structure

* Removed two knative specific tutorials

* modified knative quickstart check

* pptx

* Corrected gh workflow

* updated documentation for deployment patterns

Author: sriumcp

.github/workflows/knative-e2e-tests.yaml

@@ -60,6 +60,7 @@ jobs:
     - name: Check if experiment is complete and successful
       run: |
         export ITER8=$(pwd)
+        export EXPERIMENT=quickstart-exp
         source $ITER8/samples/knative/quickstart/check.sh
 
   canary:
@@ -159,8 +160,8 @@ jobs:
         export ITER8=$(pwd)
         source $ITER8/samples/knative/conformance/check.sh
         
-  canary-progressive-helm:
-    name: progressive canary experiment using helm
+  progressive:
+    name: progressive experiment
     runs-on: ubuntu-latest
     steps:
     - name: Checkout repository
@@ -219,6 +220,54 @@ jobs:
         export ITER8=$(pwd)
         source $ITER8/samples/knative/canaryprogressive/check.sh
 
+  fixedsplit:
+    name: fixed-split experiment
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v2
+    
+    - uses: engineerd/[email protected]
+    - name: platform setup
+      run: |
+        export ITER8=$(pwd)
+        $ITER8/samples/knative/quickstart/platformsetup.sh contour
+
+    - name: create Knative service and readiness check
+      run: |
+        export ITER8=$(pwd)
+        kubectl apply -f $ITER8/samples/knative/quickstart/baseline.yaml
+        kubectl apply -f $ITER8/samples/knative/fixed-split/experimentalservice.yaml
+        kubectl wait --for=condition=Ready ksvc/sample-app --timeout=240s
+
+    - name: create Fortio job and create experiment
+      run: |
+        export ITER8=$(pwd)
+        sed -i "s/6000s/120s/g" $ITER8/samples/knative/quickstart/fortio.yaml
+        URL_VALUE=$(kubectl get ksvc sample-app -o json | jq .status.address.url)
+        sed "s+URL_VALUE+${URL_VALUE}+g" $ITER8/samples/knative/quickstart/fortio.yaml | kubectl apply -f -
+        
+        # Wait for Fortio to be ready
+        pod_name=$(kubectl get pods --selector=job-name=fortio -o jsonpath='{.items[*].metadata.name}')
+        kubectl wait --for=condition=Ready pods/"$pod_name" --timeout=240s
+
+        # Define metrics
+        kubectl apply -f $ITER8/samples/knative/quickstart/metrics.yaml
+
+        # Starting the experiment
+        kubectl apply -f $ITER8/samples/knative/fixed-split/experiment.yaml
+
+    - name: Sleep until end of experiment
+      run: |
+        sleep 150.0
+        kubectl get experiment fixedsplit-exp -o yaml
+    
+    - name: Check if experiment is complete and successful
+      run: |
+        export ITER8=$(pwd)
+        export EXPERIMENT=fixedsplit-exp
+        source $ITER8/samples/knative/quickstart/check.sh
+
   canary-fixedsplit-kustomize:
     name: fixedsplit canary experiment with kustomize
     runs-on: ubuntu-latest

mkdocs/docs/concepts/buildingblocks.md

@@ -104,7 +104,7 @@ Iter8 can optionally **promote the recommended version** at the end of an experi
 
 ## Resource config tools
 
-Iter8 can be easily easily with Helm and Kustomize. This integration is especially useful if you use these tools for configuring Kubernetes resources needed for releases of your app/ML model.
+Iter8 can be easily integrated with Helm and Kustomize. This integration is especially useful if you use these tools for configuring Kubernetes resources needed for releases of your app/ML model.
 
 === "Helm charts"
     An experiment that uses `helm` charts for version promotion is illustrated below.

mkdocs/docs/getting-started/quick-start.md

@@ -4,7 +4,7 @@ template: main.html
 
 # Quick Start
 
-!!! tip "Scenario: A/B testing and progressive deployment"
+!!! tip "Scenario: A/B testing"
     [A/B testing](../../concepts/buildingblocks/#testing-pattern) enables you to compare two versions of an app/ML model, and select a winner based on a (business) reward metric and objectives (SLOs). In this tutorial, you will:
 
     1. Perform A/B testing.
@@ -241,6 +241,7 @@ Choose the K8s stack over which you are performing the A/B testing experiment.
     ```shell
     kubectl apply -f $ITER8/samples/knative/quickstart/baseline.yaml
     kubectl apply -f $ITER8/samples/knative/quickstart/experimentalservice.yaml
+    kubectl wait --for=condition=Ready ksvc/sample-app
     ```
 
     ??? info "Look inside baseline.yaml"
@@ -351,7 +352,6 @@ Choose the K8s stack over which you are performing the A/B testing experiment.
     Generate requests using [Fortio](https://github.com/fortio/fortio) as follows.
 
     ```shell
-    kubectl wait --for=condition=Ready ksvc/sample-app
     # URL_VALUE is the URL where your Knative application serves requests
     URL_VALUE=$(kubectl get ksvc sample-app -o json | jq .status.address.url)
     sed "s+URL_VALUE+${URL_VALUE}+g" $ITER8/samples/knative/quickstart/fortio.yaml | kubectl apply -f -