forked from paritytech/substrate
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvalues.yaml
59 lines (49 loc) · 1.43 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
# set tag manually --set image.tag=latest
image:
repository: parity/substrate
tag: latest
pullPolicy: Always
basepath: /substrate
# if set to true a service account for substrate will be created
rbac:
enable: true
name: substrate
# name of the statefulset
app: substrate
listen_node_port: true
nodes:
replicas: 2
args:
# name and data directory are set by the chart itself
# key and node-key may be provided on commandline invocation
#
# - --chain
# - krummelanke
# serve rpc within the local network
# - fenced off the world via firewall
# - used for health checks
- --rpc-external
- --ws-external
# - --log
# - sub-libp2p=trace
validator: {}
# providing 'keys' string via --set commandline parameter will run the nodes
# in validator mode (--validator).
#
# name, key and node-key can be given in a base64 encoded keyfile string (at
# validator.keys) which has the following format:
#
# substrate-0-name <node-name>
# substrate-0-key <key-seed>
# substrate-0-node-key <node-secret-key>
# substrate-1-name <node-name>
# substrate-1-key <key-seed>
# substrate-1-node-key <node-secret-key>
#
# pod names are canonical. changing these or providing different amount of
# keys than the replicas count will lead to behavior no one ever has
# experienced before.
# maybe adopt resource limits here to the nodes of the pool
# resources:
# memory: "5Gi"
# cpu: "1.5"