Avalanche Archive Mainnet Node Guide
This Quick Start guide has not yet been updated for Launchpad V2.
This guide is intended to be an end to end walk-through of running an Avalanche Archive Mainnet Node in an existing Kubernetes cluster. Sync times are reported to be in the range of 3 weeks on dedicated hardware.
Prerequisites
All the Launchpad Prerequisites apply if running a Kubernetes cluster using Launchpad
, so be sure to read them first. This guide can be used with existing Kubernetes clusters as well.
For avalanche workload you will need:
- CPU: 4 Cores / 8 Threads
- RAM: 16 GiB
- Storage: 3 TiB NVMe SSD
If running a Kubernetes cluster using Launchpad
- Check that the cluster is running and healthy - review Quick Start guide for more info.
- In your private infra repo pull in latest
launchpad-starter
changes
task launchpad:pull-upstream-starter
- Pull in
latest-core
changes
task launchpad:update-core
Check default values- double-check values and update as needed in
<your-private-copy-of-launchpad-starter>/helmfiles/release-names/arbitrum-mainnet/avalanche-archive-trace-mainnet-0.yaml
Deploy avalanche-mainnet namespace
task releases:apply avalanche-mainnet
Deploying with helm in a Kubernetes cluster outside Launchpad
You can find blockchain related helm packages here
By default avalanche is told what type of node to run by the following default toml
config:
configTemplate: |
# Store configuration in toml format
snowman-api-enabled = "false"
eth-apis = [
"eth",
"eth-filter",
"net",
"web3",
"internal-eth",
"internal-blockchain",
"internal-transaction",
"internal-tx-pool",
"internal-account"
]
metrics-enabled = "true"
pruning-enabled = "false"
state-sync-enabled = "false"
Override the above config by providing a new one in a values file and deploy:
helm repo add graphops http://graphops.github.io/launchpad-charts
helm install --dry-run avalanche graphops/avalanche:latest --namespace avalanche-mainnet --values avalanche-mainnet.yaml