Network Deployments on Solo

One-shot Falcon Deployment

Mon, 01 Jan 0001 00:00:00 +0000

Overview

One-shot Falcon deployment is Solo’s YAML-driven one-shot workflow. It uses the same core deployment pipeline as solo one-shot single deploy, but lets you inject component-specific flags through a single values file.

One-shot use Falcon deployment when you need a repeatable advanced setup, want to check a complete deployment into source control, or need to customise component flags without running every Solo command manually.

Falcon is especially useful for:

Falcon Values File Reference

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This page catalogs the Solo CLI flags accepted under each top-level section of a Falcon values file. Each entry corresponds to the command-line flag that the underlying Solo subcommand accepts.

Sections map to subcommands as follows:

Section	Solo subcommand
`network`	`solo consensus network deploy`
`setup`	`solo consensus node setup`
`consensusNode`	`solo consensus node start`
`mirrorNode`	`solo mirror node add`
`explorerNode`	`solo explorer node add`
`relayNode`	`solo relay node add`
`blockNode`	`solo block node add`

All flag names must be written in long form with double dashes (for example, --release-tag). Flags left empty ("") or matching their default value are ignored by Solo at argument expansion time.

Step-by-Step Manual Deployment

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Manual deployment lets you deploy each Solo network component individually, giving you full control over configuration, sequencing, and troubleshooting. Use this approach when you need to customise specific steps, debug a component in isolation, or integrate Solo into a bespoke automation pipeline.

Prerequisites

Before proceeding, ensure you have completed the following:

System Readiness — your local environment meets all hardware and software requirements (Docker, kind, kubectl, helm, Solo).

Dynamically add, update, and remove Consensus Nodes

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This guide covers how to dynamically manage consensus nodes in a running Solo network - adding new nodes, updating existing ones, and removing nodes that are no longer needed. All three operations can be performed without taking the network offline.

Prerequisites

Before proceeding, ensure you have:

A running Solo network. If you don’t have one, deploy using one of the following methods:
1. Quickstart - single command deployment using solo one-shot single deploy.
2. Manual Deployment - step-by-step deployment with full control over each component.
Set the required environment variables as described below: