Skip to main content

Avalanche Archive Mainnet Node Guide

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.


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

  1. Check that the cluster is running and healthy - review Quick Start guide for more info.
  2. In your private infra repo pull in latest launchpad-starter changes
task launchpad:pull-upstream-starter
  1. Pull in latest-core changes
task launchpad:update-core
  1. 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

  2. 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 = [
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
helm install --dry-run avalanche graphops/avalanche:latest --namespace avalanche-mainnet --values avalanche-mainnet.yaml