Removes Pipelineruns from tests folder (awslabs#375)

This commit removes pipelines runs for test folder.

Signed-off-by: Ashish Ranjan <[email protected]>

Author: ashishranjan738

tests/README.md

@@ -67,7 +67,106 @@ EOF
 ```
 
 ### Scheduling recurrent test runs.
-For scheduling recurrent test runs a cron job is used to trigger the pipeline from the pipelinerun template. Reffer to the for a sample cron job and pipelinerun temaple. [example.yaml](pipelineruns%2Feks%2Fexample.yaml)
+To schedule recurrent test runs, you can leverage cron-job to trigger a pipeline run using trigger-template. Please refer to below example for sample cron job and pipelinerun template.
+
+```
+cat <<EOF | kubectl apply -f -
+---
+apiVersion: batch/v1beta1
+kind: CronJob
+metadata:
+  name: awscli-eks-load-5k-example
+  namespace: tekton-pipelines
+spec:
+  schedule: "13 15 * * *"
+  jobTemplate:
+    spec:
+      template:
+        spec:
+          containers:
+            - name: curl
+              image: curlimages/curl
+              args: ["curl", "-X", "POST", "--data", "{}", "el-awscli-eks-load-5k.tekton-pipelines.svc.cluster.local:8080"]
+          restartPolicy: Never
+---
+apiVersion: triggers.tekton.dev/v1alpha1
+kind: TriggerBinding
+metadata:
+  name: awscli-eks-load-5k
+  namespace: tekton-pipelines
+spec:
+  params:
+    - name: servicerole
+      value: <service role ARN. Example of Service Role- https://github.com/awslabs/kubernetes-iteration-toolkit/blob/main/tests/assets/eks_service_role.json>
+---
+apiVersion: triggers.tekton.dev/v1alpha1
+kind: EventListener
+metadata:
+  name: awscli-eks-load-5k
+  namespace: tekton-pipelines
+spec:
+  serviceAccountName: tekton-triggers
+  triggers:
+    - name: cron
+      bindings:
+        - ref: awscli-eks-load-5k
+      template:
+        ref: awscli-eks-load-5k
+---
+apiVersion: triggers.tekton.dev/v1alpha1
+kind: TriggerTemplate
+metadata:
+  name: awscli-eks-load-5k
+  namespace: tekton-pipelines
+spec:
+  resourcetemplates:
+    - apiVersion: tekton.dev/v1beta1
+      kind: PipelineRun
+      metadata:
+        generateName: awscli-eks-load-5k-
+      spec:
+        pipelineRef:
+          name: awscli-eks-cl2loadtest-with-addons
+        timeout: 9h0m0s
+        workspaces:
+          - name: source
+            emptyDir: {}
+          - name: config
+            volumeClaimTemplate:
+              spec:
+                accessModes:
+                  - ReadWriteOnce
+                storageClassName: gp2
+                resources:
+                  requests:
+                    storage: 1Gi
+          - name: results
+            emptyDir: {}
+        params:
+          - name: cluster-name
+            value: "awscli-eks-load-100"
+          - name: desired-nodes
+            value: "100"
+          - name: pods-per-node
+            value: "10"
+          - name: nodes-per-namespace
+            value: "100"
+          - name: cl2-load-test-throughput
+            value: "20"
+          - name: results-bucket
+            value: <replace it a s3 bucket to store test results>
+          - name: slack-message
+            value: "You can monitor here - https://tekton.scalability.eks.aws.dev/#/namespaces/tekton-pipelines/pipelineruns ;5k node "
+          - name: slack-hook
+            value: <slack hook url>
+          - name: vpc-cfn-url
+            value: "https://raw.githubusercontent.com/awslabs/kubernetes-iteration-toolkit/main/tests/assets/amazon-eks-vpc.json"
+        podTemplate:
+          nodeSelector:
+            kubernetes.io/arch: amd64
+        serviceAccountName: tekton-pipelines-executor
+EOF
+```
 
 ### Test Images