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: README.md
+30-11Lines changed: 30 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -112,15 +112,27 @@ We will use this to deploy into Kubernetes.
112
112
113
113
### Setup
114
114
115
-
To do so, you must first inject a Personal Access Token to your Manetu instance as a secret into your cluster for the tool to use, like so:
115
+
#### Credentials
116
+
117
+
You must inject a Personal Access Token to your Manetu instance as a Kubernetes [Secret](https://kubernetes.io/docs/concepts/configuration/secret/) into your cluster for the tool to use, like so:
You must also deploy the query/bindings you wish to use as a Kubernetes [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/). The ConfigMap should have two bindings named 'bindings.csv' and 'query.sparql', which we will use to inject the files into our deployment in the next step.
For convenience, this file may be found in this repository as [kubernetes/job.yaml](./kubernetes/job.yaml). You may apply this like so:
175
+
176
+
For convenience, this file is available in this repository as [kubernetes/job.yaml](./kubernetes/job.yaml). You may apply this like so:
157
177
158
178
```shell
159
179
kubectl apply -f kubernetes/job.yaml
160
180
```
161
-
> N.B. The container supports overriding the query and bindings with the environment variables LOADTEST_QUERY and LOADTEST_BINDINGS, respectively. You may replace the default examples using techniques such as mounting Kubernetes [ConfigMaps as volumes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#add-configmap-data-to-a-specific-path-in-the-volume). This is left as an exercise to the reader.
162
181
163
182
### Obtaining results
164
183
165
-
You may use 'kubectl logs' to obtain the test results once the run is completed. First, obtain the name of the pod, like so:
184
+
Once the job is completed, you may use 'kubectl logs' to obtain the test results. First, obtain the name of the pod, like so:
0 commit comments