forked from testground/testground
-
Notifications
You must be signed in to change notification settings - Fork 0
/
env-example.toml
52 lines (45 loc) · 1.66 KB
/
env-example.toml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
## This is an example .env.toml to illustrate how the testground's .env.toml is
## formatted and used.
# The aws table specifies credentials and settings for the AWS integration,
# which may be used by several components.
#
["aws"]
region = "<aws region>"
["dockerhub"]
repo = "repo to be used for testground"
username = "username"
access_token = "docker hub access token"
# You can set parameters for runners and builders that apply to your
# environment. They will be applied with the following precedence (highest
# to lowest):
#
# 1. CLI --run-param, --build-param flags.
# 2. .env.toml.
# 3. Test plan manifest.
# 4. Runner defaults (applied by the runner).
#
[runners."cluster:k8s"]
run_timeout_min = 10
testplan_pod_cpu = "100m"
testplan_pod_memory = "100Mi"
collect_outputs_pod_cpu = "100m"
collect_outputs_pod_memory = "100Mi"
autoscaler_enabled = false
provider = "aws"
sysctls = [
"net.core.somaxconn=10000",
]
[runners."local:docker"]
ulimits = [
"nofile=1048576:1048576",
]
[daemon]
listen = ":8080"
[daemon.scheduler]
task_timeout_min = 20
task_repo_type = "disk"
# The endpoint refers to the `testground-daemon` service, so depending on your setup, this could be, for example, a Load Balancer fronting the kubernetes cluster and forwarding proper requests to the `tg-daemon` service, or a simple port forward to your local workstation:
# kubectl port-forward service/testground-daemon 8080:8042, where 8042 is the port on which the tg-daemon is listening, and 8080 is a port on your local workstation
[client]
endpoint = "http://localhost:8080"
user = "myname"