forked from fangpenlin/eth2-validator-helm
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values.yaml
290 lines (237 loc) · 6.71 KB
/
values.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
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
# Default values for eth2-validator.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
openethereum:
enabled: true
defaultArgs: [
"--jsonrpc-interface=all",
"--metrics",
"--metrics-interface=all",
"--base-path=/var/data/"
]
extraArgs: []
persistent:
enabled: true
accessModes: [ "ReadWriteOnce" ]
size: 256Gi
storageClassName: standard
replicaCount: 1
image:
repository: openethereum/openethereum
tag: v3.1.1
pullPolicy: IfNotPresent
# The network to connect to
network: goerli
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
serviceAccount:
# Specifies whether a service account should be created
create: true
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name:
podSecurityContext:
fsGroup: 1000
securityContext:
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
runAsUser: 1000
runAsGroup: 1000
service:
enabled: true
type: ClusterIP
hostPort:
# When hostPort is enabled, the 30303 p2p ports for TCP/UDP will be open on the node where
# the pod lives. As a result, you won't be able to run two instances of openethereum
# on the same node. In that case, you would probably want to use affinity to avoid
# schedule two of them on the same host. Also, you need to configure your network firewall
# rule to allow 30303 port access
enabled: true
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
livenessProbe:
httpGet:
path: /metrics
port: metrics
initialDelaySeconds: 30
failureThreshold: 5
periodSeconds: 10
readinessProbe:
httpGet:
path: /metrics
port: metrics
initialDelaySeconds: 30
failureThreshold: 5
periodSeconds: 10
nodeSelector: {}
tolerations: []
affinity: {}
beacon:
enabled: true
defaultArgs: [
"lighthouse",
"beacon",
"--datadir", "/var/data",
"--staking",
"--metrics",
"--disable-upnp",
"--http-address", "0.0.0.0",
"--metrics-address", "0.0.0.0",
]
extraArgs: []
persistent:
enabled: true
accessModes: [ "ReadWriteOnce" ]
size: 128Gi
storageClassName: standard
replicaCount: 1
image:
repository: sigp/lighthouse
tag: v1.1.3
pullPolicy: IfNotPresent
# The network to connect to
network: pyrmont
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
serviceAccount:
# Specifies whether a service account should be created
create: true
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name:
podSecurityContext:
fsGroup: 1000
securityContext:
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
runAsUser: 1000
runAsGroup: 1000
service:
enabled: true
type: NodePort
livenessProbe:
httpGet:
path: /metrics
port: metrics
initialDelaySeconds: 30
failureThreshold: 5
periodSeconds: 10
readinessProbe:
httpGet:
path: /metrics
port: metrics
initialDelaySeconds: 30
failureThreshold: 5
periodSeconds: 10
hostPort:
# When hostPort is enabled, the 9000 p2p ports for TCP/UDP will be open on the node where
# the pod lives. As a result, you won't be able to run two instances of beacon
# on the same node. In that case, you would probably want to use affinity to avoid
# schedule two of them on the same host. Also, you need to configure your network firewall
# rule to allow 9000 port access
enabled: true
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
nodeSelector: {}
tolerations: []
affinity: {}
validator:
enabled: true
keystoreSecretName: "eth2-validator-keystore"
passwordSecretName: "eth2-validator-password"
defaultArgs: [
"lighthouse",
"validator",
# Without this, slashing_protection.sqlite could be missing. In context of K8S, you are not
# going to share the same volume anyway, so it shouldn't matter to have slashing_protection.sqlite
# or not
"--init-slashing-protection",
"--datadir", "/var/data",
"--metrics",
"--metrics-address", "0.0.0.0",
]
extraArgs: []
persistent:
enabled: true
accessModes: [ "ReadWriteOnce" ]
size: 32Gi
storageClassName: standard
image:
repository: sigp/lighthouse
tag: v1.1.3
pullPolicy: IfNotPresent
# The network to connect to
network: pyrmont
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
serviceAccount:
# Specifies whether a service account should be created
create: true
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name:
podSecurityContext:
fsGroup: 1000
securityContext:
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
runAsUser: 1000
runAsGroup: 1000
service:
enabled: true
type: ClusterIP
livenessProbe:
httpGet:
path: /metrics
port: metrics
initialDelaySeconds: 30
failureThreshold: 5
periodSeconds: 10
readinessProbe:
httpGet:
path: /metrics
port: metrics
initialDelaySeconds: 30
failureThreshold: 5
periodSeconds: 10
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
nodeSelector: {}
tolerations: []
affinity: {}