📄️ Change node image
To change the image used for bitcoind, CLN or LND:
📄️ Persist node data
By default nodes in scaling lightning are ephemereal and will lost their data between network or node restarts and upgrades.
📄️ Direct (g)RPC connection to nodes
One of the prerequisits for scaling lightning is to have traefik installed on the cluster to enable ingress into the cluster from outside. The command specified in the Getting Started references an values file where we specify 40 endpoints to use with nodes in the network. One of those endpoints is used for scaling lightning itself to talk to nodes from the cli or library. This leaves 39 endpoints which can be allocated to bitcoind or lightning nodes to gain direct external acccess to their (g)RPC services.
📄️ Running in the cloud
An advantage of running on kubernetes is that running in the cloud is as easy as running locally. Create a cluster in the cloud and download the cluster configuration file. If you make this your default configuration then nothing else special needs to be done. Scaling lightning cli and library will use the default cluster.
📄️ Running on github actions
As a scaling lightning network can be setup and interacted with from code it lends itself to being usable for end to end or functional tests running on Github actions (or CI/CD tool of choice).