For a Mac mini server, write the handbook before the setup grows
A project can start with before adding more machines. Commands can usually be repeated later, but the reasons behind each choice and the mistakes made along the way are easy to lose.
The example setup uses 3 small nodes to run one Kubernetes cluster. All nodes use , which avoids SSH and a normal shell, so s become the main way to manage the machines.
The roles are split into 1 and 2 workers. The main lesson is that rebuilding a node is less important than preserving why the node was built that way.
Key points
- Start the with written decisions, not only installed software.
- The example uses 3 small nodes in one Kubernetes cluster.
- is managed through instead of SSH and a normal shell.
- The setup has 1 and 2 workers.
- For a , the practical habit is to document setup reasons and recovery steps early.