Node on a cloud VM
A node runs on a plain virtual machine; Kubernetes adds nothing for a single validator. Terraform for each provider is in verana-deploy-examples: a shared cloud-init that installs the published binary, restores the latest snapshot and starts the systemd service, and one folder per provider for the VM, the data volume, the firewall and a static address. This page gives the sizing.
| Full node (RPC for your own services) | Validator | |
|---|---|---|
| CPU, memory | 4 vCPU, 8 GB | 4 vCPU, 16 GB |
| Disk | 200 GB SSD, grows with chain history | same, plus a separate volume for backups |
| Network | 26656 open to peers; 26657 and 1317 only to your services | 26656 to your sentries only; no public RPC |
| Snapshots | daily disk snapshot | daily, plus key material in offline custody |
Providers: OVHcloud Public Cloud b3-16 or a dedicated server; AWS m6i.xlarge with gp3; Google Cloud n2-standard-4 with pd-ssd; Azure Standard_D4s_v5 with Premium SSD. Pick the region closest to your sentries.
Then follow Join testnet and, for validators, Become a validator and the sentry architecture.