Two fixes, no new command and no change to the piped output of the parity cases.

Fixed

• The Lo driver names the host bridge in a form the kernel accepts. A project network name of more than 15 bytes (IFNAMSIZ-1) made docker network create fail with "numerical result out of range", so lo provision stopped before a single node existed. A name that fits stays as it is, and every existing bridge keeps its name; a longer one becomes lo-<12 hex of its sha256>, in the Go driver and the bash tree alike. The bash tree takes the digest from sha256sum or shasum -a 256, and fails with a message when a host has neither (#226).
• The kubeone driver's Robot check counts the descriptor's #cloud.root servers, read from the provider's dump beside the manifest. Before, any declared static worker counted as bare metal, so a cloud-only cluster with one cloud worker refused to render its addons without Hetzner Robot credentials it had no use for. When the dump is missing, the render warns and skips the check instead of refusing (#225).

Upgrade

b update in a project that pins github.com/kernpilot/lok8s/lo, or download the asset and its checksum, verify, then install:

V=v0.7.2; A=lo-linux-amd64.tar.gz        # pick your tag and platform
curl -fsSLO "https://github.com/kernpilot/lok8s/releases/download/${V}/${A}"
curl -fsSLO "https://github.com/kernpilot/lok8s/releases/download/${V}/checksums.txt"
sha256sum --ignore-missing -c checksums.txt
tar -xzf "${A}" lo && install -m 0755 lo ~/.local/bin/lo