THORChain Docs
DEVSNODES
Search…
Introduction
Learn
How It Works
Roles
RUNE
Ecosystem
Frequently Asked Questions
THORChain Finance
Liquidity Model
Synthetic Asset Model
Lending and Savings
Stablecoin
Network
Emission Schedule
Incentive Pendulum
Governance
Security
THORChain Name Service
Constants and Mimir
Developers
Dev Docs moved to Dedicated Site
Chain Clients
Overview
UTXO Chains
EVM Chains
BFT Chains
THORNodes
THORNode Overview
Cluster Launcher
Setup - Linode
Setup - Azure
Setup - Hetzner Bare Metal
Setup - Google Cloud
Setup - HCloud
Setup - Digital Ocean
Setup - AWS
Deploying
Joining
Managing
Pooled THORNodes
Alerting
Leaving
🛑
Emergency Procedures
✔️ CHECKLIST
Get Involved
Contribute
Community Telegram
Dev Discord
Powered By GitBook
Cluster Launcher
Deploying a THORNode with Kubernetes

Deploy a Kubernetes cluster

In order to deploy all the different services and provide a high availability environment to operate your node, Kubernetes is the preferred scheduling platform. Any production-grade Kubernetes cluster can be used to run and deploy a THORNode. You need your Kubernetes provider to offer external load balancers services type features. Azure, Digital Ocean, GCE, OpenStack are compatible with external load balancers.
Terraform is a type of domain-specific language (DSL) used to describe code infrastructure. It is designed to make it easier to create/destroy infrastructure hosted locally or by a provider.
This Terraform deployment will deploy a Kubernetes cluster using your VPS provider credentials and EKS service. The cluster will have autoscaling capabilities, which means you don’t have to deal with how many nodes you need to deploy to run your THORNode services.
All the default configurations used in these instructions are for a production environment with enough resources to run your THORNode in good conditions.
LINUX/MAC is the preferred method of setup.
Windows should choose either:
  1. 1.
    Deploy a THORNode from a Linux VPS.
  2. 2.
    Use Windows Subsystem for Linux - https://docs.microsoft.com/en-us/windows/wsl/about​

Steps

There are three important steps to getting your node set up, deployed and churned in.

Repository Management

Your repository should be organised as follows:
./thornode-ops
|./cluster-launcher
|./node-launcher
All of your set up commands are run in cluster-launcher and all of your deploying/joining/managing/leaving commands are run from node-launcher

Running Two or More Nodes

To prevent a catastrophic mistake in handling multiple nodes, set them up on different machines, or use different user profiles on your machine, or in the least, use different repos:
./thornode-ops
|./cluster-launcher
|./node-launcher
./thornode-ops2
|./cluster-launcher
|./node-launcher
All of your commands can now be run separately.
It is heavily advised to not set up nodes on the same provider. Deploy 1 node on Azure, 1 node on Digital Ocean etc.
THORNodes - Previous
THORNode Overview
Next
Setup - Linode
Last modified 5mo ago
Export as PDF
Copy link
Edit on GitHub
Outline
Deploy a Kubernetes cluster
Steps
Repository Management
Running Two or More Nodes