Task 5: Add and verify the nano worker node

In this task, you will apply the knowledge gained from adding the agx node to independently add and verify a second worker node, named nano. This guide will provide fewer explicit commands and instead prompt you to recall the steps from the previous tasks, reinforcing the learning process.

Before you start

It is essential that your team is prepared for this verification process.

Make sure that:

Task 4 (node verification) has been successfully completed.
The cluster is healthy with the k3smain and agx nodes in a Ready state.
You have the Node Token and Control Plane IP Address that you retrieved and saved from Task 3.

Objective

Your goal is to add and verify a second worker node, named nano, by applying the procedures you mastered in the previous tasks.

Procedure

Refer back to the detailed instructions from Task 3 and Task 4 to complete this objective.

Apply the steps from Task 3 ("Adding worker nodes") to the nano node. Ensure you use the correct node name (nano) and its specific internal IP address in the installation command.
Once the installation is complete, apply the steps from Task 4 ("Verifying worker node addition") to confirm from the control plane that the nano node is Ready and to assign it the worker role.

The task is complete when kubectl get nodes shows three healthy nodes: one control plane and two labeled workers (agx and nano).

Accomplishments

Second Worker Node Integrated:

A second worker node, nano, was successfully joined to the cluster. Its status was verified as Ready and it is visible to the control plane.

Consistent Role Assignment

The nano node was configured with the node-role.kubernetes.io/worker label, ensuring consistent role designation across all worker nodes in the cluster.

Cluster Topology Expanded

The cluster has been successfully scaled from a two-node to a three-node topology, now consisting of one control-plane node and two worker nodes.

Multi-Node Operational Readiness

The health and connectivity of the complete three-node cluster have been validated. The system is confirmed to be operational and ready for application deployment.

The system is now a fully operational, three-node Kubernetes cluster. The current state, comprising of one control-plane node and two verified worker nodes, provides the necessary foundation for deploying containerized applications with replication and exploring fault tolerance.

Reflection

Please take a moment to write down any questions, issues, or doubts you encountered during this milestone.
This will help guide the next discussion and ensure everyone is on the same page before moving forward.

Next Steps

exit (ctrl + a then d) from the screen session.
exit from the ssh session on the nano.
Return to the terminal on your computer.
The node token can now be deleted, as node addition is complete.
Rejoin the common Discord lobby to await further instructions or support your peers.

Last modified: 23 June 2025