Skip to content

Commit 02a15b3

Browse files
authored
docs: add instructions to add nodes (#2040)
1 parent 1427c95 commit 02a15b3

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

README.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -289,6 +289,36 @@ task talos:upgrade-k8s
289289
# e.g. task talos:upgrade-k8s
290290
```
291291

292+
### ➕ Adding a node to your cluster
293+
294+
At some point you might want to expand your cluster to run more workloads and/or improve the reliability of your cluster. Keep in mind it is recommended to have an **odd number** of control plane nodes for quorum reasons.
295+
296+
You don't need to re-bootstrap the cluster to add new nodes. Follow these steps:
297+
298+
1. **Prepare the new node**: Review the [Stage 1: Machine Preparation](#stage-1-machine-preparation) section and boot your new node into maintenance mode.
299+
300+
2. **Get the node information**: While the node is in maintenance mode, retrieve the disk and MAC address information needed for configuration:
301+
302+
```sh
303+
talosctl get disks -n <ip> --insecure
304+
talosctl get links -n <ip> --insecure
305+
```
306+
307+
3. **Update the configuration**: Read the documentation for [talhelper](https://budimanjojo.github.io/talhelper/latest/) and extend the `talconfig.yaml` file manually with the new node information (including the disk and MAC address from step 2).
308+
309+
4. **Generate and apply the configuration**:
310+
311+
```sh
312+
# Render your talosconfig based on the talconfig.yaml file
313+
task talos:generate-config
314+
315+
# Apply the configuration to the node
316+
task talos:apply-node IP=?
317+
# e.g. task talos:apply-node IP=10.10.10.10
318+
```
319+
320+
The node should join the cluster automatically and workloads will be scheduled once they report as ready.
321+
292322
## 🤖 Renovate
293323
294324
[Renovate](https://www.mend.io/renovate) is a tool that automates dependency management. It is designed to scan your repository around the clock and open PRs for out-of-date dependencies it finds. Common dependencies it can discover are Helm charts, container images, GitHub Actions and more! In most cases merging a PR will cause Flux to apply the update to your cluster.

0 commit comments

Comments
 (0)