Deploying a THORNode and its associated services.
Now you have a Kubernetes cluster ready to use, you can install the THORNode services.
- Running Kubernetes cluster
- Kubectl configured, ready and connected to running cluster
node-launcherrepo. All commands in this section are to be run inside of this repo.
git clone https://gitlab.com/thorchain/devops/node-launcher
git checkout master
Install Helm 3 if not already available on your current machine:
To deploy all tools, metrics, logs management, Kubernetes Dashboard, run the command below.
To destroy all those resources run the command below.
If you are successful, you will see the following message:
If there are any errors, they are typically fixed by running the command again.
It is important to deploy the tools first before deploying the THORNode services as some services will have metrics configuration that would fail and stop the THORNode deployment.
You have multiple commands available to deploy different configurations of THORNode. You can deploy testnet or chaosnet/mainnet. The commands deploy the umbrella chart
thornode-stackin the background in the Kubernetes namespace
thornode-testnetfor testnet) by default.
If successful, you will see the following:
You are now ready to join the network:
Use the following useful commands to view and debug accordingly. You should see everything running and active. Logs can be retrieved to find errors:
kubectl get pods -n thornode
kubectl get pods --all-namespaces
kubectl logs -f <pod> -n thornode
Kubernetes should automatically restart any service, but you can force a restart by running:
kubectl delete pod <pod> -n thornode
- thornode: Umbrella chart packaging all services needed to run a fullnode or validator THORNode.
This should be the only chart used to run THORNode stack unless you know what you are doing and want to run each chart separately (not recommended).
- thor-daemon: THORNode daemon
- thor-api: THORNode API
- thor-gateway: THORNode gateway proxy to get a single IP address for multiple deployments
- bifrost: Bifrost service
- midgard: Midgard API service
- binance-daemon: Binance fullnode daemon
- bitcoin-daemon: Bitcoin fullnode daemon
- ethereum-daemon: Ethereum fullnode daemon
- chain-daemon: as required for supported chains
- elastic: ELK stack, deperecated. Use elastic-operator chart
- elastic-operator: ELK stack using operator for logs management
- prometheus: Prometheus stack for metrics
- loki: Loki stack for logs
- kubernetes-dashboard: Kubernetes dashboard