Skip to main content

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:

ParameterIs optionalDefaultDefault
testkube-api.storage.endpointyestestkube-minio-service-testkube:9000URL of the S3 bucket
testkube-api.storage.accessKeyIdyesminioAccess Key ID
testkube-api.storage.accessKeyyesminio123Access Key
testkube-api.storage.locationyesRegion
testkube-api.storage.tokenyesS3 Token
testkube-api.storage.SSLyesfalseIndicates whether SSL communication is to be enabled
testkube-api.storage.scrapperEnabledyestrueIndicates whether executors should scrape artifacts

The API Server accepts the following environment variables:

STORAGE_ENDPOINT
STORAGE_ACCESSKEYID
STORAGE_SECRETACCESSKEY
STORAGE_LOCATION
STORAGE_TOKEN
STORAGE_SSL
SCRAPPERENABLED

Which can be set while installing with Helm:

helm install --create-namespace my-testkube testkube/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