This chart bootstraps a bitcoin node on a Kubernetes cluster using the Helm package manager. Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully validate blocks and transactions. It also includes a wallet and graphical user interface, which can be optionally built.
Further information about Bitcoin Core is available here.
helm repo add bitcoind https://chrisrun.github.io/bitcoind-chart/
helm upgrade --install bitcoind bitcoind/bitcoind -n bitcoind --version 1.1.0 --create-namespaceThis will setup a full node and
This chart bootstraps a bitcoin deployment on a Kubernetes cluster using the Helm package manager.
- Kubernetes 1.20+
- Helm 3.2.0+
To install the chart with the release name bitcoind
$ helm repo add bitcoind https://chrisrun.github.io/bitcoind-chart/
$ helm upgrade --install bitcoind bitcoind/bitcoind -n bitcoind --create-namespaceThese commands deploy a bitcoin full node on the Kubernetes cluster using the default configuration.
Tip List all releases using
helm list
helm list -n bitcoindTo uninstall/delete the bitcoind deployment
$ helm delete bitcoind -n bitcoindThe command removes all the Kubernetes components associated with the chart and deletes the release.
| Name | Description | Value |
|---|---|---|
image.repository |
the image repository to be used | chr1st1anh/bitcoind |
image.tag |
the image version | 22.0 |
image.digest |
the image digest, use this if there is no private registry | "" |
image.pullPolicy |
pull policy | IfNotPresent |
| Name | Description | Value |
|---|---|---|
configuration.rpcuser |
optional, if not quoted it will be generated | "" |
configuration.txindex |
If you want to be able to access any transaction with commands like gettransaction, you need to configure Bitcoin Core to build a complete transaction index, which can be achieved with the txindex=1. You can't use a txindex with a pruned blockchain. Pruning will throw away scanned blocks. | 1 |
configuration.server |
the image repository to be used | 1 |
configuration.network |
can be any of mainnet, regtest, signet or testnet, if omitted mainnet will be used only a single network per deployment is supported | mainnet |
configuration.prune |
Autopprune (-prune=550) allows you to reduce your historical blockchain data to a given target (in MB, example uses 550 which is the minimum). You can't throw away all blocks because you may need to "roll back a couple of block" if there is a chain reorganisation. If you set prune=1 (== manual mode), you can then manually prune your blockchain (use RPC call pruneblockchain ) | "" |
configuration.passwordLength |
The length of the password for the RPC user | 50 |
| Name | Description | Value |
|---|---|---|
persistence.accessMode |
Access mode of the mounted drive. | ReadWriteOnce |
persistence.size |
Size of the mounted drive. Bitcoin on mainnet should have more than 500GB to work for a while. | 600GB |
persistence.storageClass |
The storage class used to provision the drive. | gp2 |
| Name | Description | Value |
|---|---|---|
resources.requests.cpu |
Limits and requests for CPU resources are measured in cpu units. | 250m |
resources.requests.memory |
You can express memory as a plain integer or as a fixed-point number using one of these quantity suffixes: E, P, T, G, M, k. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki. | 1G |
resources.limits.cpu |
Limits and requests for CPU resources are measured in cpu units. | 250m |
resources.limits.memory |
You can express memory as a plain integer or as a fixed-point number using one of these quantity suffixes: E, P, T, G, M, k. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki. | 1G |