-
Notifications
You must be signed in to change notification settings - Fork 0
/
values-cluster-large.yaml
111 lines (103 loc) · 2.92 KB
/
values-cluster-large.yaml
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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
# tracetest relies on NATS as a service bus for communication between its components.
nats:
config:
cluster:
enabled: true
name: "nats"
replicas: 3
# tracetest-frontend is a simple frontend service that serves the UI.
# it is a static web app serving service, so the load is minimal.
tracetest-frontend:
replicaCount: 2
resources:
limits:
cpu: 250m
memory: 512Mi
requests:
cpu: 100m
memory: 128Mi
# tracetest-core handles most of the API requests and test workloads.
# It is composed of 6 services. Each of those can be individually configured with replicas and limits,
# but in general they all require the same resources.
tracetest-core:
# deploymentReplicas defines the replica count for each service if not overridden in the deployments section.
deploymentReplicas: 2
# deploymentResources defines the default resources for each service if not overridden in the deployments section.
deploymentResources:
limits:
cpu: 500m
memory: 2048Mi
requests:
cpu: 250m
memory: 512Mi
# tracetest-cloud handles accounts, environments and non test related data, but more importantly
# it serves as the control plane for the agents, so it is better to have it highly available.
tracetest-cloud:
deployment:
replicas: 3
resources:
limits:
cpu: 500m
memory: 2048Mi
requests:
cpu: 250m
memory: 512Mi
# tracetest-agent-operator is the service in charge of launching and stoppin serverless agents.
# This service is very lightway, and in general doesn't require multiple replicas.
tracetest-agent-operator:
deployment:
replicas: 1
resources:
limits:
cpu: 250m
memory: 512Mi
requests:
cpu: 100m
memory: 128Mi
# tracetest-monitor-operator is the service in charge of scheduling synthetic monitoring tasks.
# This service is very lightway, and in general doesn't require multiple replicas.
tracetest-monitor-operator:
deployment:
replicas: 1
resources:
limits:
cpu: 250m
memory: 512Mi
requests:
cpu: 100m
memory: 128Mi
# tracetest-auth is a collection of services that handle authentication and authorization.
tracetest-auth:
# keto manages authorization
keto:
replicaCount: 1
deployment:
resources:
limits:
cpu: 500m
memory: 2048Mi
requests:
cpu: 250m
memory: 512Mi
# kratos handles authentication and SSO
kratos:
replicaCount: 1
deployment:
resources:
limits:
cpu: 500m
memory: 2048Mi
requests:
cpu: 250m
memory: 512Mi
# oathkeeper is a reverse proxy that handles authentication and authorization
oathkeeper:
replicaCount: 1
deployment:
resources:
limits:
cpu: 500m
memory: 2048Mi
requests:
cpu: 250m
memory: 512Mi