You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+124Lines changed: 124 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,130 @@ Generate node identities, configure consensus, and emit a Besu genesis.
6
6
7
7
The helm chart to run this on Kubernetes / OpenShift can be found [here](./charts/network-bootstrapper/README.md)
8
8
9
+
### Deployment modes
10
+
11
+
Two deployment paths are supported: fully auto-generated artefacts or supplying your own genesis/static peers while sourcing node keys from an external secret store such as Conjur.
The bootstrapper Job generates the genesis file, static-nodes list, validator keys, and faucet account and publishes them as ConfigMaps/Secrets consumed by the Besu StatefulSets.
35
+
36
+
#### External genesis/static peers with Conjur-managed keys
37
+
38
+
Genesis and static peer data can be committed to version control while validator and faucet private keys are injected at deployment time. The chart expects the validator count in `artifacts.external.validators` to match `global.validatorReplicaCount`.
39
+
40
+
Create a Summon manifest describing the Conjur variables and a templated values file that references the injected environment variables:
Summon resolves the secrets in memory, `envsubst` renders them into a transient values file, and Helm creates the ConfigMaps/Secrets required by the Besu nodes. The temporary file is removed once the release is installed.
98
+
99
+
### Local artefact generation with Docker
100
+
101
+
Run the bootstrapper container locally to capture all artefacts before loading them into Conjur or another secret manager.
The container writes artefacts beneath `/workspace/out/<timestamp>`; mounting a host directory captures the results. Each validator and faucet file is emitted as JSON for ease of parsing. After loading secrets into Conjur, reference the same variables in your Summon configuration and embed the exported `genesis.json` and `static-nodes.json` within the Helm values file.
Copy file name to clipboardExpand all lines: README.tpl
+124Lines changed: 124 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -6,4 +6,128 @@ Generate node identities, configure consensus, and emit a Besu genesis.
6
6
7
7
The helm chart to run this on Kubernetes / OpenShift can be found [here](./charts/network-bootstrapper/README.md)
8
8
9
+
### Deployment modes
10
+
11
+
Two deployment paths are supported: fully auto-generated artefacts or supplying your own genesis/static peers while sourcing node keys from an external secret store such as Conjur.
The bootstrapper Job generates the genesis file, static-nodes list, validator keys, and faucet account and publishes them as ConfigMaps/Secrets consumed by the Besu StatefulSets.
35
+
36
+
#### External genesis/static peers with Conjur-managed keys
37
+
38
+
Genesis and static peer data can be committed to version control while validator and faucet private keys are injected at deployment time. The chart expects the validator count in `artifacts.external.validators` to match `global.validatorReplicaCount`.
39
+
40
+
Create a Summon manifest describing the Conjur variables and a templated values file that references the injected environment variables:
Summon resolves the secrets in memory, `envsubst` renders them into a transient values file, and Helm creates the ConfigMaps/Secrets required by the Besu nodes. The temporary file is removed once the release is installed.
98
+
99
+
### Local artefact generation with Docker
100
+
101
+
Run the bootstrapper container locally to capture all artefacts before loading them into Conjur or another secret manager.
The container writes artefacts beneath `/workspace/out/<timestamp>`; mounting a host directory captures the results. Each validator and faucet file is emitted as JSON for ease of parsing. After loading secrets into Conjur, reference the same variables in your Summon configuration and embed the exported `genesis.json` and `static-nodes.json` within the Helm values file.
Copy file name to clipboardExpand all lines: charts/network/charts/network-bootstrapper/README.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,13 @@ A Helm chart for Kubernetes
15
15
| Key | Type | Default | Description |
16
16
|-----|------|---------|-------------|
17
17
| affinity | object |`{}`||
18
+
| artifacts.external.faucet.address | string |`""`| Faucet account address stored in the `besu-faucet-address` ConfigMap when `source` equals `external`. |
19
+
| artifacts.external.faucet.privateKey | string |`""`| Faucet private key stored in the `besu-faucet-private-key` Secret when `source` equals `external`. |
20
+
| artifacts.external.faucet.publicKey | string |`""`| Faucet account public key stored in the `besu-faucet-pubkey` ConfigMap when `source` equals `external`. |
21
+
| artifacts.external.genesis | object |`{}`| Besu genesis document rendered into the `besu-genesis` ConfigMap when `source` equals `external`. |
22
+
| artifacts.external.staticNodes | list |`[]`| Collection of enode URIs persisted to the `besu-static-nodes` ConfigMap when `source` equals `external`. |
23
+
| artifacts.external.validators | list |`[]`| Validator node definitions providing the data expected by the nodes chart. Each entry must include `address`, `publicKey`, `privateKey`, and `enode`. |
24
+
| artifacts.source | string |`"generated"`| Determines how Besu network artifacts are populated. Use `generated` to run the job or `external` to supply values manually. |
18
25
| fullnameOverride | string |`"bootstrapper"`| Override for the fully qualified resource name generated by helpers. |
0 commit comments