When running Predator, it is possible to retrieve and update some of the service's configuration
during runtime with the /config endpoint, please check the API reference for more details.
Below are variables Predator can be configured with.
The predator-runner docker image that will run the test
✓
zooz/predator-runner:$LATEST_TAGGED_VERSION
RUNNER_CPU
runner_cpu
Number of CPU use by the each runner
✓
1
RUNNER_MEMORY
runner_memory
Max memory to use by each runner
✓
256
DEFAULT_EMAIL_ADDRESS
default_email_address
Default email to send final report to, address can be configured
✓
ALLOW_INSECURE_TLS
allow_insecure_tls
If true, don't fail requests on unverified server certificate errors
✓
false
DELAY_RUNNER_MS
delay_runner_ms
Delay the predator runner from sending http requests (ms)
✓
INTERVAL_CLEANUP_FINISHED_CONTAINERS_MS
interval_cleanup_finished_containers_ms
Interval (in ms) to search and delete finished tests containers. Value of 0 means no auto clearing enabled
✓
0
CUSTOM_RUNNER_DEFINITION
custom_runner_definition
Custom json that will be merged with the kubernetes/metronome predator runner job definition. See FAQ for usage examples.
API
STREAMING_EXCLUDED_ATTRIBUTES
streaming_excluded_attributes
Attribute names to exclude from being produced in the resource to streaming platform
API
MAX_UPLOAD_FILE_SIZE_MB
Maximum file size (in megabytes) that is allowed for uploading CSV files
10
Note
RUNNER_DOCKER_IMAGE (zooz/predator-runner:$TAGGED_VERSION) should match the Predator's version running in order to be fully compatible with all features.