The in_use flag found on the Hardware CRD in the Tink repository is hyperloaded dependent on the client reading/updating it. In Cluster API it indicates a machine has been provisioned while in the Tinkerbell stack it has loose semantics that generally prevent DHCP being served for that Hardware.
We want to rearchitect this flag, possibly remove it in favor of simpler solutions, to make understanding the system state easier.
The
in_useflag found on theHardwareCRD in the Tink repository is hyperloaded dependent on the client reading/updating it. In Cluster API it indicates a machine has been provisioned while in the Tinkerbell stack it has loose semantics that generally prevent DHCP being served for that Hardware.We want to rearchitect this flag, possibly remove it in favor of simpler solutions, to make understanding the system state easier.