A control plane does not have to be a website
Infrastructure needs a place where intent, inventory and repeatable workflows come together. That role can live in a shell-native tool when operators already administer Linux through SSH and want native system state to remain visible.
Keep operational boundaries explicit
A controller can coordinate Fleet membership, KVM guests, networking and application workflows without turning every member into a separate administration service.
Temporary web access can still have a place
Some tasks benefit from a browser, but short-lived, scoped access for diagnostics or database administration is different from exposing the entire management plane permanently.
Recovery should survive guest failure
Hypervisor console and noVNC workflows are useful because they remain available when a guest SSH service or network configuration is broken.