mak3r
commented
4 years ago I think this is all possible. In some situations, the device is going to be plugged into a wired network and wifi configuration is not the first thing that needs to happen. I'd like to try and develop a process model for turnkey which lays out a formal set of steps for configuration similar to a supervisor or init system in linux. The turnkey process in the MVP simply needs to bootstrap device hardware (wifi NIC) and then configure user space software (k3s). I'm sure there are other areas we should address like security config and there needs to be some manner of controller that handles dependencies. That is all done specific to the solution right now. I think it's important to understand that the wifi setup designed for the MVP is replacing the process that is more typically done by a systemd or supervisor.
Outside of an MVP, I can see a scenario where an operator/admin would be provisioning multiple turnkey devices at a single time. This would break the current deployment model as it utilizes mDNS as the discovery mechanism.
Possible ways to work around this: a) create additional option to set a hostname per device (could write a separate issue just for this) b) create additional options to bypass mDNS discovery / DHCP by setting a static IP address. b*) A bad configuration could potentially lead to a bad network initialization which would require a failover mode where the hotspot would be re-enabled for additional configuration.