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
OPCT-326: collector: gather kube-burner data for basic perf profiles (#67)
Collect kube-burner profiles to with a simple execution to measure basic
performance from clusters in controlled environment (aka know
providers/CI) to be used as a baseline while evaluating partner
clusters.
Total time increased in the workflow: 9 minutes
Total data collected (additional): ~512K
Those profiles have been used to collect performance report in internal
documentation: [OPCT-276](https://issues.redhat.com/browse/OPCT-276)
Collector plugin/step is the final step of the default conformance workflow
4
+
executed by OPCT.
3
5
4
-
Build and push (from root directory of project):
6
+
The step collects artifacts such as:
7
+
8
+
- e2e metadata executed by openshift-tests for previous steps - sent to the collector pod as a artifact server, saved with prefix `artifacts_e2e-*`
9
+
- must-gather: used as a baseline to evaluate cluster information, and etcd performance during the conformance tests. Must-gather is the first data collected—running before performance tests—so our report won’t be impacted by non-e2e workloads.
10
+
-[camgi](https://github.com/elmiko/camgi.rs) report: generates camgi report if it is available in the running architecture
11
+
- run etcd FIO tool: to evaluate disk one-off performance of control plane nodes, and sample of compute/worker nodes
12
+
- kube-burner: run standard profiles to execute performance tests, collecting metrics and data to local index
13
+
14
+
## Prerequisites
15
+
16
+
- Download latest version of opct
17
+
18
+
### Build your custom image
19
+
Build and push (from the root directory):
5
20
6
21
```sh
7
22
make build-plugin-collector PLATFORMS=linux/amd64 COMMAND=push
8
23
```
24
+
25
+
## Usage
26
+
27
+
### Run individual collectors - kube-burner
28
+
29
+
It's possible to run individual collector by customizing the plugin manifest.
30
+
31
+
The kube-burner manifest file `manifests/kube-burner-only.yaml` enforce flags
32
+
to prevent collecting standard data, running only kube-burner in the target cluster.
33
+
34
+
To run the standalone plugin, you can use the wrapped API of Sonobuoy including OPCT:
35
+
36
+
> Update the `image` in the podSpec manifest file `manifests/kube-burner-only.yaml`
37
+
38
+
- Run
39
+
```bash
40
+
./opct sonobuoy run -p ./artifacts-collector/manifests/kube-burner-only.yaml \
0 commit comments