You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tests/README.md
+100-1
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,106 @@ EOF
67
67
```
68
68
69
69
### Scheduling recurrent test runs.
70
-
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)
70
+
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.
value: <service role ARN. Example of Service Role- https://github.com/awslabs/kubernetes-iteration-toolkit/blob/main/tests/assets/eks_service_role.json>
101
+
---
102
+
apiVersion: triggers.tekton.dev/v1alpha1
103
+
kind: EventListener
104
+
metadata:
105
+
name: awscli-eks-load-5k
106
+
namespace: tekton-pipelines
107
+
spec:
108
+
serviceAccountName: tekton-triggers
109
+
triggers:
110
+
- name: cron
111
+
bindings:
112
+
- ref: awscli-eks-load-5k
113
+
template:
114
+
ref: awscli-eks-load-5k
115
+
---
116
+
apiVersion: triggers.tekton.dev/v1alpha1
117
+
kind: TriggerTemplate
118
+
metadata:
119
+
name: awscli-eks-load-5k
120
+
namespace: tekton-pipelines
121
+
spec:
122
+
resourcetemplates:
123
+
- apiVersion: tekton.dev/v1beta1
124
+
kind: PipelineRun
125
+
metadata:
126
+
generateName: awscli-eks-load-5k-
127
+
spec:
128
+
pipelineRef:
129
+
name: awscli-eks-cl2loadtest-with-addons
130
+
timeout: 9h0m0s
131
+
workspaces:
132
+
- name: source
133
+
emptyDir: {}
134
+
- name: config
135
+
volumeClaimTemplate:
136
+
spec:
137
+
accessModes:
138
+
- ReadWriteOnce
139
+
storageClassName: gp2
140
+
resources:
141
+
requests:
142
+
storage: 1Gi
143
+
- name: results
144
+
emptyDir: {}
145
+
params:
146
+
- name: cluster-name
147
+
value: "awscli-eks-load-100"
148
+
- name: desired-nodes
149
+
value: "100"
150
+
- name: pods-per-node
151
+
value: "10"
152
+
- name: nodes-per-namespace
153
+
value: "100"
154
+
- name: cl2-load-test-throughput
155
+
value: "20"
156
+
- name: results-bucket
157
+
value: <replace it a s3 bucket to store test results>
158
+
- name: slack-message
159
+
value: "You can monitor here - https://tekton.scalability.eks.aws.dev/#/namespaces/tekton-pipelines/pipelineruns ;5k node "
0 commit comments