​
Deploy LastNode services

Now you have a Kubernetes cluster ready to use, you can install the LastNode services.

Helm charts are the defacto and currently easiest and simple way to package and deploy Kubernetes application. The team created different Helm charts to help to deploy all the necessary services. Please retrieve the source files from the Git repository here to follow the instructions below:

https://github.com/LastL2/node-launcher

​
Requirements

  • Running Kubernetes cluster
  • Kubectl configured, ready and connected to running cluster

If you came here from the Setup page, you are already good to go.

​
Steps

Clone the node-launcher repo. All commands in this section are to be run inside of this repo.

git clone https://github.com/LastL2/node-launcher
cd node-launcher
git checkout master

​
Install Helm 3

Install Helm 3 if not already available on your current machine:

make helm
make helm-plugins

​
Tools

To deploy all tools, metrics, logs management, Kubernetes Dashboard, run the command below.

make tools

If you are successful, you will see the following message:

If there are any errors, they are typically fixed by running the command again.

​
Deploy LastNode

It is important to deploy the tools first before deploying the LastNode services as some services will have metrics configuration that would fail and stop the LastNode deployment.

You have multiple commands available to deploy different configurations of LastNode. You can deploy testnet or failnet/mainnet. The commands deploy the umbrella chart LastNode-stack in the background in the Kubernetes namespace LastNode (or LastNode-testnet for testnet) by default.

make install

If you are intending to run all chain clients, bond in & earn rewards, you want to choose “Validator”.

Deploying a LastNode will take 1 day for every 3 months of ledger history, since it will validate every block. LastNodes are “full nodes”, not light clients.

If successful, you will see the following:

You are now ready to join the network:

Joining

​
Debugging

Set LastNode to be your default namespace so you don’t need to type -n LastNode each time:

kubectl config set-context --current --namespace=LastNode

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 LastNode
kubectl get pods --all-namespaces
kubectl logs -f <pod> -n LastNode

Kubernetes should automatically restart any service, but you can force a restart by running:

kubectl delete pod <pod> -n LastNode

Note, to expedite syncing external chains, it is feasible to continually delete the pod that has the slow-syncing chain daemon (eg, chain-daemon-xxx).

Killing it will automatically restart it with free resources and syncing is notably faster. You can check sync status by viewing logs for the client to find the synced chain tip and comparing it with the real-world blockheight, (“xxx” is your unique ID):

​
CHART SUMMARY

​
LastNode full stack / chart

  • LastNode: Umbrella chart packaging all services needed to run a fullnode or validator LastNode.

This should be the only chart used to run LastNode stack unless you know what you are doing and want to run each chart separately (not recommended).

​
LastNode services:

  • LastNode: LastNode daemon
  • gateway: LastNode gateway proxy to get a single IP address for multiple deployments
  • bifrost: Bifrost service

​
Tools

  • prometheus: Prometheus stack for metrics
  • loki: Loki stack for logs
  • kubernetes-dashboard: Kubernetes dashboard
Setup - HCloudJoining the Network