Artifacts Storage
Testkube allows you to save supported files generated by your tests, which we call Artifacts.
The executor will scrape the files and store them in Minio. The executor will create a bucket named by execution ID and collect all files that are stored in the location specific to each executor.
The available configuration parameters in Helm charts are:
| Parameter | Is optional | Default | Default |
|---|---|---|---|
| testkube-api.storage.endpoint | yes | testkube-minio-service-testkube:9000 | URL of the S3 bucket |
| testkube-api.storage.accessKeyId | yes | minio | Access Key ID |
| testkube-api.storage.accessKey | yes | minio123 | Access Key |
| testkube-api.storage.location | yes | Region | |
| testkube-api.storage.token | yes | S3 Token | |
| testkube-api.storage.SSL | yes | false | Indicates whether SSL communication is to be enabled. |
| testkube-api.storage.scrapperEnabled | yes | true | Indicates whether executors should scrape artifacts. |
| testkube-api.storage.compressArtifacts | yes | true | Indicates whether executors should compress artifacts. |
The API Server accepts the following environment variables:
STORAGE_ENDPOINT
STORAGE_BUCKET
STORAGE_ACCESSKEYID
STORAGE_SECRETACCESSKEY
STORAGE_LOCATION
STORAGE_REGION
STORAGE_TOKEN
STORAGE_SSL
SCRAPPERENABLED
COMPRESSARTIFACTS
Which can be set while installing with Helm:
helm install --create-namespace my-testkube kubeshop/testkube --set STORAGE_ENDPOINT=custom_value
Alternatively, these values can be read from Kubernetes secrets and set:
- env:
- name: STORAGE_ENDPOINT
secret:
secretName: test-secret