-
Notifications
You must be signed in to change notification settings - Fork 66
/
README.md.gotmpl
40 lines (25 loc) · 1.16 KB
/
README.md.gotmpl
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
{{ template "chart.header" . }}
{{ template "chart.deprecationWarning" . }}
{{ template "chart.versionBadge" . }}{{ template "chart.typeBadge" . }}
{{ template "chart.description" . }}
{{ template "chart.homepageLine" . }}
{{ template "chart.sourcesSection" . }}
{{ template "chart.requirementsSection" . }}
{{ template "chart.valuesSection" . }}
# Examples
## Connecting to the holesky test network
```yaml
extraArgs:
- --chain=holesky
```
## Exposing the P2P service via NodePort
This will make your node accessible via the Internet using a service of type [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport).
When using `p2pNodePort.enabled` the exposed IP address on your ENR record will be the "External IP" of the node where the pod is running.
**Limitations:** You can only run a single replica per chart deployment when using `p2pNodePort.enabled=true`.If you need N nodes, simply deploy the chart N times.
Currently reth doesn't allow you to announce a a different discovery port, which would be a requirement to run multiple replicas within the same chart.
```yaml
replicas: 1
p2pNodePort:
enabled: true
port: 31000
```