yeke.io · docs
Adding machines
If you have a bare server, YEKE can add it to the inventory, reach it over SSH and build a Kubernetes cluster on it. This page covers how the inventory and that first contact work.
The machine inventory
Admin → Machines. Requires administrator rights.
A machine record carries an address, an SSH user and port, labels, and — after the first connection — the fingerprint of the host key.
A record cannot be edited afterwards. If the address or user changes, you create a new record. There is one reason: the identity of a machine record is also the identity of every past job attached to it, and editing a field later would make historical jobs appear to belong to a different machine.
First contact: pinning the host key
There are three states, told in three different voices — because the third one is a security event.
| State | Meaning | What you do |
|---|---|---|
| Not pinned | Nothing has connected yet. Not a fault — a stage. | Start the first job; the key gets pinned then. |
| Pinned | The fingerprint is on record and compared on every connection. | Compare it once against the machine's own ssh-keygen output. |
| Changed | The machine is presenting a different key. Either it was rebuilt, or somebody is in the middle. | Do not connect. Confirm the rebuild first. |
The fingerprint is shown in a copyable form on screen; that is the only way the comparison can be made:
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub
Building a cluster
A build job is started from machines in the inventory.
- The job proceeds step by step and each step reports its own state on screen; the log stream is live.
- A finished job does not add the cluster to your inventory by itself — you connect the new cluster with the Connecting a cluster steps.
- Permissions remain a separate step. A newly built cluster follows the same model as everything else — see Permissions.
Want to see these screens live?
The provisioning flow depends on your setup and hardware; a short demo is the fastest way through it.