Add the option to install a large-cluster manifest and cordon control plane to dedicated machines (#1632)

This change allows users to install Substrate on larger clusters. It
adds a `--cluster-size` flag to enable more t-shirt-style sizing in the
future to accommodate clusters of different sizes.

It also adds a --cordon-control-plane flag that allows
taints/tolerances/antiaffinity/node labels to have each control plane
element run on its own dedicated machine.

Fixes #<issue_number_goes_here>

> It's a good idea to open an issue first for discussion.

- [ ] Tests pass
- [ ] Appropriate changes to documentation are included in the PR
This commit is contained in:
Max Smythe
2026-09-24 23:39:01 +00:00
committed by GitHub
parent 14c0c136bc
commit d6d2a0fa1d
32 changed files with 1490 additions and 104 deletions
+9
View File
@@ -366,6 +366,15 @@ Handles actor-aware routing and automatic re-animation.
* **Latency**: The data plane is optimized for sub-100ms activation by bypassing Kubernetes' eventual consistency and performing atomic physical assignments.
### Control Plane Isolation
Control plane components can be kept on nodes of their own,
away from the workers. Those nodes carry the label
`ate.dev/workloadType=ate-control-plane` and the taint
`ate.dev/workloadType=ate-control-plane:NoSchedule`; when
configured via the installer, the control plane
workloads select the label and tolerate the taint.
## Actor Lifecycle
The lifecycle of an actor follows a state-driven sequence. A request reaches an